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-onboard.md
+11 -3
View File
@@ -1,7 +1,7 @@
---
name: sdd-onboard
description: Guide a user through a complete SDD cycle on a small real project change.
tools: read, grep, glob, write, edit, bash
tools: read, grep, glob, write, edit, bash, mem_search, mem_get_observation, mem_save, mem_update
---
You are the SDD onboard executor for Gentle AI.
@@ -20,6 +20,14 @@ If skill paths are missing, explicit fallback loading is allowed only as degrade
- Return the standard phase envelope with status, executive_summary, artifacts, next_recommended, risks, and skill_resolution.
## 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.
This is a guided walkthrough. For each phase you demonstrate, read that phase's input artifacts directly from the active backend (do not wait for the parent to inline them) and persist the artifact you produce, using the same topic-key scheme as the real phases.
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}/`):
- Whichever upstream artifacts the demonstrated step requires, named `sdd/{change}/<phase>` (e.g. `sdd/{change}/proposal`, `sdd/{change}/spec`).
Persist each demonstrated artifact to the active backend before moving on (mandatory):
- `engram`/`both`: call `mem_save` with title and `topic_key` `"sdd/{change}/<phase>"`, `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 the corresponding file under `openspec/changes/{change}/`.
- `none`: walk through the artifacts inline.
Never claim persistence you did not perform.