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-06-10 15:03:59 +02:00
parent e7934c64c2
commit 7fc599484d
10 changed files with 165 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.pi/agent/agents/sdd-proposal.md
+13
View File
@@ -13,6 +13,19 @@ Use your assigned executor/phase skill for this SDD phase. For project/user skil
If skill paths are missing, explicit fallback loading is allowed only as degraded self-healing. Report `skill_resolution` as `paths-injected`, `fallback-registry`, `fallback-path`, or `none`; fallbacks mean the parent should pass indexed paths next time.
- Read exploration and project standards before writing.
- In interactive SDD mode, do not make the agent decide silently whether the proposal is "clear enough". Offer the user a proposal question round before finalizing the proposal: explain that the questions are meant to improve the PRD/proposal by uncovering business rules, implications, impact, edge cases, and product tradeoffs. Let the user answer, skip, correct the framing, or ask for a second question round.
- Proposal-shaping questions should uncover business/product/PRD understanding, not harness mechanics. Cover the smallest useful subset of:
1. business problem: what pain, opportunity, user confusion, or operational cost makes this change worth doing now;
2. target users and situations: who is affected, in which workflow, at what moment, and with what level of urgency;
3. business rules: policies, permissions, thresholds, lifecycle rules, compliance/security expectations, or domain invariants the proposal must respect;
4. product outcome: what should feel, work, or become possible after the change;
5. current-state gap: what is wrong, inconsistent, missing, ad hoc, or hard to explain today;
6. implications and impact: which teams, workflows, data, UX expectations, support burden, or operational processes may be affected;
7. edge cases: empty states, partial data, failures, permissions, slow paths, unusual customers, migration states, or conflicting user needs;
8. decision gaps: which product unknowns would make the proposal ambiguous, risky, or easy to overbuild;
9. scope boundaries and non-goals: what belongs in the first product slice, what is later refinement, and what must stay unchanged even if related;
10. business risk or tradeoff: what downside matters most if the proposal chooses the wrong direction.
- Prefer 3–5 concrete product questions per round. After the first answers, summarize the resulting proposal assumptions and ask whether the user wants to correct anything or run a second question round. Do not ask about test commands, PR shape, changed-line budget, or other harness decisions unless the user explicitly asks to discuss delivery. If blocked from asking directly, write a `## Proposal question round` section in the proposal result with the proposed questions and assumptions needing user review.
- 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.