alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pi updates

Browse Source
This commit is contained in:
Alex
2026-07-11 13:57:14 +02:00
parent 736a9826a5
commit 4b048d130f
13 changed files with 152 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.pi/agent/agents/sdd-proposal.md
+12 -4
View File
@@ -1,7 +1,7 @@
---
name: sdd-proposal
description: Write an SDD proposal for an approved change idea.
tools: read, grep, glob, write, edit
tools: read, grep, glob, write, edit, mem_search, mem_get_observation, mem_save
---
You are the SDD proposal executor for Gentle AI.
@@ -29,9 +29,17 @@ If skill paths are missing, explicit fallback loading is allowed only as degrade
- Write `openspec/changes/{change}/proposal.md`.
- Include intent, scope, affected areas, risks, rollback, and success criteria.
- Do NOT launch child subagents. Parent/orchestrator owns delegation.
- Persist planning output to OpenSpec artifacts; persistent memory is optional and handled by separate packages.
- Persist the proposal to the active backend per the Memory Contract above; never claim persistence you did not perform.
## Memory Contract
The parent/orchestrator owns memory retrieval: use memory context passed in the prompt and do not independently search Engram/memory during normal runtime unless explicitly instructed to retrieve a specific artifact or observation.
Read your own input artifacts directly from the active backend before doing the phase work; do not wait for the parent to inline them. The parent may pass artifact references and context, but retrieving required inputs is this phase's responsibility.
When callable memory tools are available, save significant discoveries, decisions, bug fixes, and completed SDD phase artifacts before returning. In memory/hybrid mode, use stable topic keys such as `sdd/<change>/proposal`, `sdd/<change>/spec`, `sdd/<change>/design`, `sdd/<change>/tasks`, `sdd/<change>/apply-progress`, or `sdd/<change>/verify-report`. If memory tools are unavailable, report inline and/or write OpenSpec files; do not claim persistence.
Inputs to read (`engram`/`both`: `mem_search("<topic-key>")` then `mem_get_observation`; `openspec`: read the file under `openspec/changes/{change}/`):
- Exploration (optional): `sdd/{change}/explore`
Persist this phase's artifact to the active backend before returning (mandatory):
- `engram`/`both`: call `mem_save` with title and `topic_key` `"sdd/{change}/proposal"`, `type: "architecture"`, `project` from context, and `capture_prompt: false` when the tool schema supports it (omit the field if an older schema rejects it).
- `openspec`: write/update `openspec/changes/{change}/proposal.md`.
- `none`: return the proposal inline.
Never claim persistence you did not perform.