sdd-cli 0.1.0

package/flows/RETAIL_STORE.md

@@ -0,0 +1,33 @@
+# Flow: Retail store
+
+## Goal
+Support in-store sales, inventory, and customer management in a reliable, low-latency system.
+
+## Discovery prompts
+- What POS systems and devices are in scope?
+- What inventory sources are authoritative?
+- What promotions and discount rules exist?
+- How should returns and exchanges work?
+- What offline mode is required?
+
+## Required artifacts
+- `requirement.md` with store operations constraints
+- `functional-spec.md` for POS, inventory, and staff flows
+- `technical-spec.md` for device integration and offline sync
+- `architecture.md` for store-local resiliency
+- `test-plan.md` for offline/online transitions
+
+## Risk and compliance
+- Inventory drift across locations
+- Offline mode data loss
+- PCI compliance for payments
+
+## Acceptance criteria examples
+- Store can operate for 8+ hours offline.
+- Inventory reconciles within SLA after reconnect.
+- Payment flows pass compliance checks.
+
+## Recommended outputs
+- POS workflow diagram
+- Offline sync strategy
+- Store ops checklist

package/flows/SOCIOLOGY.md

@@ -0,0 +1,33 @@
+# Flow: Sociology research
+
+## Goal
+Design a study or analysis of social behavior with clear methods and ethical safeguards.
+
+## Discovery prompts
+- What is the research question?
+- What population or group is studied?
+- What method is used (survey, interviews, observation)?
+- What ethical requirements apply?
+- What outcomes or hypotheses are tested?
+
+## Required artifacts
+- `requirement.md` with research scope
+- `functional-spec.md` for research workflow
+- `technical-spec.md` for data collection and analysis tools
+- `architecture.md` for dataset and analysis pipeline
+- `test-plan.md` for validity and bias checks
+
+## Risk and compliance
+- Informed consent and privacy
+- Sampling bias
+- Misinterpretation of data
+
+## Acceptance criteria examples
+- Method aligns with research question.
+- Data collection respects consent and privacy.
+- Findings are reproducible and transparent.
+
+## Recommended outputs
+- Ethics checklist
+- Survey or interview guide
+- Data analysis plan

package/flows/STATE_ADMIN.md

@@ -0,0 +1,33 @@
+# Flow: State administration
+
+## Goal
+Deliver reliable public services with strict compliance, transparency, and audit trails.
+
+## Discovery prompts
+- What service is being delivered (permits, benefits, licenses)?
+- What laws and regulations apply?
+- What are the SLA requirements for response times?
+- Who are the actors (citizens, clerks, supervisors)?
+- What data must be retained and for how long?
+
+## Required artifacts
+- `requirement.md` with legal constraints and SLA targets
+- `functional-spec.md` for service request and approval flows
+- `technical-spec.md` for identity and access management
+- `architecture.md` for resiliency and data governance
+- `test-plan.md` for SLA compliance and failure scenarios
+
+## Risk and compliance
+- Legal compliance and transparency
+- Accessibility for public services
+- Disaster recovery requirements
+
+## Acceptance criteria examples
+- Requests are tracked end-to-end with timestamps.
+- Service availability meets SLA targets.
+- Decisions can be audited by authorized parties.
+
+## Recommended outputs
+- Citizen request tracking
+- Compliance dashboard
+- Audit-ready reports

package/flows/STUDENT_UNIVERSITY.md

@@ -0,0 +1,33 @@
+# Flow: Student (university)
+
+## Goal
+Plan and deliver a project or research task with clear milestones, requirements, and documentation.
+
+## Discovery prompts
+- What is the course or program requirement?
+- What is the deliverable format (report, prototype, presentation)?
+- What is the grading rubric or success criteria?
+- What is the timeline and milestones?
+- Who are the stakeholders (advisor, team members)?
+
+## Required artifacts
+- `requirement.md` with assignment constraints
+- `functional-spec.md` for user stories or research tasks
+- `technical-spec.md` for tools and stack
+- `architecture.md` for system or study design
+- `test-plan.md` or validation plan
+
+## Risk and compliance
+- Plagiarism rules and citation requirements
+- Data privacy for any collected data
+- Academic integrity constraints
+
+## Acceptance criteria examples
+- Deliverable meets rubric and formatting rules.
+- All claims are supported with citations.
+- Prototype demonstrates required functionality.
+
+## Recommended outputs
+- Milestone plan
+- Research log
+- Final submission checklist

package/flows/TAXES_ADMIN.md

@@ -0,0 +1,33 @@
+# Flow: Taxes administration
+
+## Goal
+Manage tax filing, validation, audits, and compliance with strong security and traceability.
+
+## Discovery prompts
+- What tax types are supported (income, sales, corporate)?
+- What validation rules are mandatory?
+- What are the filing deadlines and penalty rules?
+- Who can access taxpayer data?
+- What integrations exist (banking, identity, government systems)?
+
+## Required artifacts
+- `requirement.md` with compliance and validation constraints
+- `functional-spec.md` for filing and audit workflows
+- `technical-spec.md` covering encryption and access controls
+- `architecture.md` with data segregation and audit trails
+- `test-plan.md` for validation accuracy and security
+
+## Risk and compliance
+- Sensitive financial data
+- Regulatory compliance and auditability
+- Fraud detection requirements
+
+## Acceptance criteria examples
+- All filings are validated against latest rules.
+- Every data access is logged and auditable.
+- Audit workflows can be triggered and tracked.
+
+## Recommended outputs
+- Filing validation engine
+- Audit case management
+- Compliance reporting

package/flows/TEACHER.md

@@ -0,0 +1,33 @@
+# Flow: Teacher (education)
+
+## Goal
+Create a system for lesson planning, assessments, and feedback with clear learning outcomes.
+
+## Discovery prompts
+- What grade levels and subjects are supported?
+- What is the grading model (rubrics, points, mastery)?
+- How are students and guardians notified?
+- Are there accessibility requirements?
+- What data privacy rules apply to students?
+
+## Required artifacts
+- `requirement.md` with learning objectives and scope
+- `functional-spec.md` covering lesson, assignment, and grading flows
+- `technical-spec.md` for integrations (LMS, email, calendars)
+- `architecture.md` for content storage and versioning
+- `test-plan.md` with grading accuracy and accessibility checks
+
+## Risk and compliance
+- Student data privacy
+- Accessibility standards
+- Content versioning and auditability
+
+## Acceptance criteria examples
+- Teachers can reuse and version lessons.
+- Students receive feedback within configured SLAs.
+- Accessibility checks are enforced for uploaded content.
+
+## Recommended outputs
+- Lesson plan templates
+- Grading rubric engine
+- Student progress analytics

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "sdd-cli",
+  "version": "0.1.0",
+  "description": "SDD-first, AI-native CLI for end-to-end delivery.",
+  "bin": {
+    "sdd-tool": "dist/cli.js",
+    "sdd": "dist/cli.js"
+  },
+  "main": "dist/cli.js",
+  "types": "dist/cli.d.ts",
+  "files": [
+    "dist",
+    "router",
+    "templates",
+    "schemas",
+    "flows"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "start": "node dist/cli.js",
+    "dev": "ts-node src/cli.ts"
+  },
+  "dependencies": {
+    "ajv": "^8.17.1",
+    "commander": "^12.1.0"
+  },
+  "devDependencies": {
+    "@types/node": "^22.13.1",
+    "ts-node": "^10.9.2",
+    "typescript": "^5.7.3"
+  }
+}

package/router/BUG_FIX.flow.md

@@ -0,0 +1,63 @@
+# Router flow: Bug fix
+
+## Entry signals
+- "bug", "issue", "error", stack trace, "crash", "regression"
+
+## Steps
+1) Ask permission to open external links or repos.
+2) If approved, fetch and summarize issue/context.
+3) Ask user perspective: what they see, expected vs actual, impact.
+4) Require repro steps, environment, severity, and recent changes.
+5) Generate 5+ solution paths with trade-offs.
+6) Ask user to choose preferred path or request `--improve`.
+7) Generate requirements and specs for the selected path.
+8) Gate implementation until test plan and quality profile are set.
+
+## Required questions
+- What is the expected behavior?
+- What is the actual behavior?
+- Steps to reproduce?
+- Environment and version details?
+- Severity and impact?
+- Recent changes or related issues?
+
+## Scripted Q/A tree
+
+### Q1: Link access
+Q: "You shared a link. Do you approve opening it?"  
+A: Yes -> fetch + summarize  
+A: No -> ask user to paste relevant details
+
+### Q2: User perspective
+Q: "Describe what you see vs what you expect."  
+A: Capture expected/actual and impact
+
+### Q3: Repro and env
+Q: "Can you share steps to reproduce and environment details?"  
+A: Capture steps, version, OS, config
+
+### Q4: Severity and scope
+Q: "How severe is this and who is impacted?"  
+A: Capture severity, user count, business impact
+
+### Q5: Path selection
+Q: "Here are 5+ possible fixes with trade-offs. Which path should we pursue?"  
+A: Capture chosen path or request `--improve`
+
+### Q6: Approval gate
+Q: "Do you approve moving to requirements and specs?"  
+A: Yes -> generate artifacts  
+A: No -> refine answers
+
+## Required outputs
+- `requirement.md` (bug scope)
+- `technical-spec.md` (root cause + fix)
+- `test-plan.md` (repro + regression)
+- `progress-log.md`
+
+## Gates
+- Repro steps required before planning
+- At least one regression test required before finish
+
+## Agents
+- Req Analyst, Tech Lead, QA

package/router/BUSINESS.flow.md

@@ -0,0 +1,57 @@
+# Router flow: Business / economics
+
+## Entry signals
+- "market", "pricing", "policy", "forecast", "economics"
+
+## Steps
+1) Interview for objective, scope, and stakeholders.
+2) Define assumptions and model approach.
+3) Generate analysis plan and outputs.
+4) Ask for approval or `--improve`.
+5) Produce sensitivity checks and executive summary.
+
+## Required questions
+- What decision will this analysis support?
+- What scope and timeframe apply?
+- What data sources are available?
+- What assumptions are acceptable?
+- What risk tolerance is required?
+
+## Required outputs
+- `requirement.md`
+- `technical-spec.md`
+- `architecture.md`
+- `test-plan.md` (sensitivity checks)
+
+## Scripted Q/A tree
+
+### Q1: Decision
+Q: "What decision will this analysis support?"  
+A: capture decision context
+
+### Q2: Scope and timeline
+Q: "What scope and timeframe apply?"  
+A: capture scope and horizon
+
+### Q3: Data sources
+Q: "What data sources are available and trusted?"  
+A: capture sources
+
+### Q4: Assumptions
+Q: "What assumptions are acceptable?"  
+A: capture assumptions
+
+### Q5: Risk tolerance
+Q: "What level of risk or uncertainty is acceptable?"  
+A: capture tolerance
+
+### Q6: Approval gate
+Q: "Approve analysis plan and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Assumptions must be explicit before analysis
+
+## Agents
+- Analyst, Economist, Critic

package/router/DATA_SCIENCE.flow.md

@@ -0,0 +1,58 @@
+# Router flow: Data science
+
+## Entry signals
+- "model", "prediction", "dataset", "ML", "analytics"
+
+## Steps
+1) Interview for objective, metrics, data sources, constraints.
+2) Define evaluation criteria and monitoring needs.
+3) Generate specs and architecture for pipelines.
+4) Ask for approval or `--improve`.
+5) Create test plan for data validation and model evaluation.
+
+## Required questions
+- What is the success metric?
+- What data sources and quality risks exist?
+- What fairness or compliance rules apply?
+- What latency/cost constraints exist?
+- How will drift be monitored?
+
+## Required outputs
+- `requirement.md`
+- `technical-spec.md`
+- `architecture.md`
+- `test-plan.md`
+- `quality.yml`
+
+## Scripted Q/A tree
+
+### Q1: Objective and metric
+Q: "What is the business or research objective and the primary metric?"  
+A: capture target metric
+
+### Q2: Data sources
+Q: "What data sources exist and what are the quality risks?"  
+A: capture sources and gaps
+
+### Q3: Constraints
+Q: "Any latency, cost, or compliance constraints?"  
+A: capture constraints
+
+### Q4: Fairness and bias
+Q: "Any fairness or bias concerns to monitor?"  
+A: capture fairness criteria
+
+### Q5: Monitoring
+Q: "How will we monitor drift post-release?"  
+A: capture monitoring plan
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Metrics and validation criteria required before plan
+
+## Agents
+- Data Scientist, MLOps, QA

package/router/DESIGN.flow.md

@@ -0,0 +1,58 @@
+# Router flow: Design / creative
+
+## Entry signals
+- "logo", "brand", "UI", "layout", "visual", "art"
+
+## Steps
+1) Interview for goals, audience, references, constraints.
+2) Define deliverables and review cadence.
+3) Generate requirements and design system structure.
+4) Ask for approval or `--improve`.
+5) Produce delivery checklist and accessibility checks.
+
+## Required questions
+- What is the message or brand?
+- Who is the audience?
+- What formats are needed?
+- What constraints or references exist?
+- What is the approval process?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md`
+- `architecture.md`
+- `test-plan.md`
+
+## Scripted Q/A tree
+
+### Q1: Message and audience
+Q: "What is the message and who is the audience?"  
+A: capture audience and goal
+
+### Q2: Deliverables
+Q: "What formats are required (logo, web, print, social)?"  
+A: capture deliverables
+
+### Q3: References
+Q: "Any style references or inspirations?"  
+A: capture references
+
+### Q4: Constraints
+Q: "What constraints apply (timeline, budget, tools)?"  
+A: capture constraints
+
+### Q5: Approval cadence
+Q: "Who approves and how often should we review?"  
+A: capture review cadence
+
+### Q6: Approval gate
+Q: "Approve requirements and move to specs?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Deliverables and approval process must be defined
+
+## Agents
+- Creative Lead, Design Systems, Critic

package/router/FLOW_TEMPLATE.md

@@ -0,0 +1,26 @@
+# Router flow template
+
+## Entry signals
+- <signal1>
+- <signal2>
+
+## Steps
+1) <step>
+2) <step>
+
+## Required questions
+- <question>
+
+## Scripted Q/A tree
+### Q1: <title>
+Q: "<question>"  
+A: <expected response>
+
+## Required outputs
+- <artifact>
+
+## Gates
+- <gate>
+
+## Agents
+- <role>

package/router/GENERIC.flow.md

@@ -0,0 +1,37 @@
+# Router flow: Generic
+
+## Entry signals
+- Unclassified or mixed intent
+
+## Steps
+1) Ask the user what they want to achieve and why.
+2) Ask if it is software, research, design, or policy.
+3) Route to the closest specialized flow.
+
+## Required questions
+- What is the goal?
+- Who is the audience?
+- What output format is expected?
+
+## Required outputs
+- Minimal `requirement.md`
+
+## Scripted Q/A tree
+
+### Q1: Goal
+Q: "What is the goal and why does it matter?"  
+A: capture objective and motivation
+
+### Q2: Domain
+Q: "Is this software, research, design, or policy?"  
+A: route to specific flow
+
+### Q3: Output
+Q: "What output format do you need?"  
+A: capture expected format
+
+## Gates
+- Must select a domain before proceeding
+
+## Agents
+- Generalist

package/router/HUMANITIES.flow.md

@@ -0,0 +1,58 @@
+# Router flow: Humanities research
+
+## Entry signals
+- "history", "sociology", "philosophy", "essay", "thesis"
+
+## Steps
+1) Interview for thesis, scope, sources, and format.
+2) Define structure and methodology.
+3) Generate plan and section outline.
+4) Ask for approval or `--improve`.
+5) Produce reading list and source checks.
+
+## Required questions
+- What is the thesis or research question?
+- What scope and timeframe apply?
+- What source types are acceptable?
+- What format is required?
+- What perspectives must be included?
+
+## Required outputs
+- `requirement.md`
+- `functional-spec.md`
+- `technical-spec.md` (citation rules)
+- `architecture.md` (structure)
+- `test-plan.md` (bias and source checks)
+
+## Scripted Q/A tree
+
+### Q1: Thesis
+Q: "What is the thesis or research question?"  
+A: capture thesis
+
+### Q2: Scope
+Q: "What period, region, or population is in scope?"  
+A: capture scope boundaries
+
+### Q3: Sources
+Q: "What sources are acceptable or required?"  
+A: capture source types and citation style
+
+### Q4: Format
+Q: "What output format is required?"  
+A: capture format
+
+### Q5: Perspectives
+Q: "Which perspectives must be included?"  
+A: capture perspectives
+
+### Q6: Approval gate
+Q: "Approve research plan and move to structure?"  
+A: Yes -> generate specs  
+A: No -> refine
+
+## Gates
+- Thesis and scope required before deep research
+
+## Agents
+- Researcher, Critic, Synthesizer

package/router/LEARN.flow.md

@@ -0,0 +1,52 @@
+# Router flow: Learn / knowledge
+
+## Entry signals
+- "learn", "teach me", "explain", "what is", "history of"
+
+## Steps
+1) Interview for depth, format, purpose, and constraints.
+2) Build a research plan and scope boundaries.
+3) Run multi-agent synthesis and critique.
+4) Deliver layered outputs (brief, deep-dive, reading list, QA).
+
+## Required questions
+- Why do you want this knowledge?
+- What depth and format do you want?
+- What focus areas matter most?
+- Time available to read or study?
+
+## Required outputs
+- `brief.md`
+- `deep-dive.md`
+- `reading-list.md`
+- `qa.md`
+- `progress-log.md`
+
+## Scripted Q/A tree
+
+### Q1: Motivation
+Q: "Why do you want to learn this topic?"  
+A: capture intent (curiosity, work, study)
+
+### Q2: Depth and format
+Q: "What depth and format do you want (overview, academic, expert)?"  
+A: select depth and output format
+
+### Q3: Focus areas
+Q: "Any specific aspects to emphasize?"  
+A: capture focus areas
+
+### Q4: Time budget
+Q: "How much time do you have to read or study?"  
+A: capture time window
+
+### Q5: Approval gate
+Q: "Approve research plan and scope?"  
+A: Yes -> run synthesis  
+A: No -> refine scope
+
+## Gates
+- Scope must be defined before deep-dive generation
+
+## Agents
+- Researcher, Critic, Synthesizer