sdd-cli 0.1.2 → 0.1.3

package/router/LEGAL.flow.md

@@ -1,58 +1,59 @@
-# Router flow: Legal / civic
-
-## Entry signals
-- "law", "court", "policy", "compliance", "contract"
-
-## Steps
-1) Interview for jurisdiction, confidentiality, and actors.
-2) Define legal constraints and evidence requirements.
-3) Generate requirements and risk checks.
-4) Ask for approval or `--improve`.
-5) Produce audit and retention guidelines.
-
-## Required questions
-- What jurisdiction and regulations apply?
-- What data is privileged or sensitive?
-- Who are the actors and access levels?
-- What retention and audit rules exist?
-- What outcomes or deliverables are required?
-
-## Required outputs
-- `requirement.md`
-- `functional-spec.md`
-- `technical-spec.md`
-- `architecture.md`
-- `test-plan.md` (access and audit checks)
-
-## Scripted Q/A tree
-
-### Q1: Jurisdiction
-Q: "What jurisdiction and regulations apply?"  
-A: capture jurisdiction and constraints
-
-### Q2: Sensitivity
-Q: "What data is privileged or sensitive?"  
-A: capture data sensitivity
-
-### Q3: Actors
-Q: "Who are the actors and access levels?"  
-A: capture roles and access
-
-### Q4: Retention
-Q: "What retention and audit rules exist?"  
-A: capture retention rules
-
-### Q5: Outcomes
-Q: "What outcomes or deliverables are required?"  
-A: capture deliverables
-
-### Q6: Approval gate
-Q: "Approve requirements and move to specs?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- Compliance constraints required before plan
-
-## Agents
-- Legal Analyst, Compliance, QA
+# Router flow: Legal / civic
+
+## Entry signals
+- "law", "court", "policy", "compliance", "contract"
+
+## Steps
+1) Interview for jurisdiction, confidentiality, and actors.
+2) Define legal constraints and evidence requirements.
+3) Generate requirements and risk checks.
+4) Ask for approval or `--improve`.
+5) Produce audit and retention guidelines.
+
+## Required questions
+- What jurisdiction and regulations apply?
+- What data is privileged or sensitive?
+- Who are the actors and access levels?
+- What retention and audit rules exist?
+- What outcomes or deliverables are required?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md`
+- `docs/ARCHITECTURE.md`
+- `test-plan.md` (access and audit checks)
+
+## Scripted Q/A tree
+
+### Q1: Jurisdiction
+Q: "What jurisdiction and regulations apply?"  
+A: capture jurisdiction and constraints
+
+### Q2: Sensitivity
+Q: "What data is privileged or sensitive?"  
+A: capture data sensitivity
+
+### Q3: Actors
+Q: "Who are the actors and access levels?"  
+A: capture roles and access
+
+### Q4: Retention
+Q: "What retention and audit rules exist?"  
+A: capture retention rules
+
+### Q5: Outcomes
+Q: "What outcomes or deliverables are required?"  
+A: capture deliverables
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Compliance constraints required before plan
+
+## Agents
+- Legal Analyst, Compliance, QA
+

package/router/SOFTWARE_FEATURE.flow.md

@@ -1,59 +1,60 @@
-# Router flow: Software feature
-
-## Entry signals
-- "feature", "build", "implement", "API", "backend", "frontend"
-
-## Steps
-1) Run discovery and acceptance criteria prompts.
-2) Generate requirements and functional spec.
-3) Generate technical spec and architecture.
-4) Ask for approval or `--improve`.
-5) Activate quality profile and test plan.
-
-## Required questions
-- What problem is solved and for whom?
-- What is in scope/out of scope?
-- What are acceptance criteria?
-- What performance/security constraints apply?
-- What is the rollout strategy?
-
-## Required outputs
-- `requirement.md`
-- `functional-spec.md`
-- `technical-spec.md`
-- `architecture.md`
-- `test-plan.md`
-- `quality.yml`
-
-## Scripted Q/A tree
-
-### Q1: Problem and users
-Q: "What problem are we solving and for whom?"  
-A: capture user/persona and objective
-
-### Q2: Scope
-Q: "What is in scope and out of scope?"  
-A: capture scope boundaries
-
-### Q3: Acceptance criteria
-Q: "What are the acceptance criteria?"  
-A: capture verifiable criteria
-
-### Q4: Constraints
-Q: "Any performance, security, or compatibility constraints?"  
-A: capture NFRs
-
-### Q5: Rollout
-Q: "How should we rollout and measure success?"  
-A: capture rollout + metrics
-
-### Q6: Approval gate
-Q: "Approve requirements and move to specs?"  
-A: Yes -> generate specs  
-A: No -> refine
-
-## Gates
-- No implementation without acceptance criteria and test plan
-
-## Agents
-- Req Analyst, Solution Architect, Tech Lead, QA
+# Router flow: Software feature
+
+## Entry signals
+- "feature", "build", "implement", "API", "backend", "frontend"
+
+## Steps
+1) Run discovery and acceptance criteria prompts.
+2) Generate requirements and functional spec.
+3) Generate technical spec and architecture.
+4) Ask for approval or `--improve`.
+5) Activate quality profile and test plan.
+
+## Required questions
+- What problem is solved and for whom?
+- What is in scope/out of scope?
+- What are acceptance criteria?
+- What performance/security constraints apply?
+- What is the rollout strategy?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md`
+- `docs/ARCHITECTURE.md`
+- `test-plan.md`
+- `quality.yml`
+
+## Scripted Q/A tree
+
+### Q1: Problem and users
+Q: "What problem are we solving and for whom?"  
+A: capture user/persona and objective
+
+### Q2: Scope
+Q: "What is in scope and out of scope?"  
+A: capture scope boundaries
+
+### Q3: Acceptance criteria
+Q: "What are the acceptance criteria?"  
+A: capture verifiable criteria
+
+### Q4: Constraints
+Q: "Any performance, security, or compatibility constraints?"  
+A: capture NFRs
+
+### Q5: Rollout
+Q: "How should we rollout and measure success?"  
+A: capture rollout + metrics
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- No implementation without acceptance criteria and test plan
+
+## Agents
+- Req Analyst, Solution Architect, Tech Lead, QA
+