sdd-cli 0.1.0 → 0.1.3

package/flows/GRAPHIC_DESIGN.md

@@ -1,33 +1,34 @@
-# Flow: Graphic design
-
-## Goal
-Deliver a visual system (brand, UI, or campaign) with clear requirements and critique loops.
-
-## Discovery prompts
-- What is the brand or message?
-- Who is the audience and context?
-- What formats are required (logo, web, print, social)?
-- What references or style directions exist?
-- What are the constraints (budget, timeline, tools)?
-
-## Required artifacts
-- `requirement.md` with audience and goals
-- `functional-spec.md` for usage scenarios
-- `technical-spec.md` for file formats and delivery specs
-- `architecture.md` for design system structure
-- `test-plan.md` for accessibility and brand consistency checks
-
-## Risk and compliance
-- Trademark conflicts
-- Accessibility and contrast compliance
-- Usage inconsistency across channels
-
-## Acceptance criteria examples
-- Color palette meets contrast ratios.
-- Logo works at small and large sizes.
-- Deliverables match required formats.
-
-## Recommended outputs
-- Brand guidelines
-- Component library
-- Asset delivery checklist
+# Flow: Graphic design
+
+## Goal
+Deliver a visual system (brand, UI, or campaign) with clear requirements and critique loops.
+
+## Discovery prompts
+- What is the brand or message?
+- Who is the audience and context?
+- What formats are required (logo, web, print, social)?
+- What references or style directions exist?
+- What are the constraints (budget, timeline, tools)?
+
+## Required artifacts
+- `requirement.md` with audience and goals
+- `functional-spec.md` for usage scenarios
+- `technical-spec.md` for file formats and delivery specs
+- `docs/ARCHITECTURE.md` for design system structure
+- `test-plan.md` for accessibility and brand consistency checks
+
+## Risk and compliance
+- Trademark conflicts
+- Accessibility and contrast compliance
+- Usage inconsistency across channels
+
+## Acceptance criteria examples
+- Color palette meets contrast ratios.
+- Logo works at small and large sizes.
+- Deliverables match required formats.
+
+## Recommended outputs
+- Brand guidelines
+- Component library
+- Asset delivery checklist
+

package/flows/HISTORY.md

@@ -1,33 +1,34 @@
-# Flow: History research
-
-## Goal
-Produce a credible historical analysis with sources, timelines, and context.
-
-## Discovery prompts
-- What period or region is in scope?
-- What is the research question or thesis?
-- What depth is required (overview vs academic)?
-- What sources are allowed or preferred?
-- What format is required (essay, lecture, timeline)?
-
-## Required artifacts
-- `requirement.md` with scope and thesis
-- `functional-spec.md` for narrative flow
-- `technical-spec.md` for citation style and source rules
-- `architecture.md` for section structure
-- `test-plan.md` for source verification and bias checks
-
-## Risk and compliance
-- Source bias and reliability
-- Misinterpretation of primary sources
-- Citation or attribution mistakes
-
-## Acceptance criteria examples
-- Claims are supported by sources.
-- Timeline is consistent and verifiable.
-- Multiple perspectives are represented.
-
-## Recommended outputs
-- Annotated bibliography
-- Timeline map
-- Thesis refinement log
+# Flow: History research
+
+## Goal
+Produce a credible historical analysis with sources, timelines, and context.
+
+## Discovery prompts
+- What period or region is in scope?
+- What is the research question or thesis?
+- What depth is required (overview vs academic)?
+- What sources are allowed or preferred?
+- What format is required (essay, lecture, timeline)?
+
+## Required artifacts
+- `requirement.md` with scope and thesis
+- `functional-spec.md` for narrative flow
+- `technical-spec.md` for citation style and source rules
+- `docs/ARCHITECTURE.md` for section structure
+- `test-plan.md` for source verification and bias checks
+
+## Risk and compliance
+- Source bias and reliability
+- Misinterpretation of primary sources
+- Citation or attribution mistakes
+
+## Acceptance criteria examples
+- Claims are supported by sources.
+- Timeline is consistent and verifiable.
+- Multiple perspectives are represented.
+
+## Recommended outputs
+- Annotated bibliography
+- Timeline map
+- Thesis refinement log
+

package/flows/LAWYER.md

@@ -1,34 +1,35 @@
-# Flow: Lawyer (legal practice)
-
-## Goal
-Build a system to manage cases, documents, deadlines, and client communication with strong audit trails.
-
-## Discovery prompts
-- What case types are supported (civil, criminal, corporate)?
-- What jurisdictions and compliance rules apply?
-- What data is sensitive or privileged?
-- Who are the actors (partners, associates, paralegals, clients)?
-- What are the legal deadlines and escalation rules?
-
-## Required artifacts
-- `requirement.md` with scope and compliance constraints
-- `functional-spec.md` including case lifecycle and document review flows
-- `technical-spec.md` detailing access control and audit logging
-- `architecture.md` with secure storage and encryption at rest
-- `test-plan.md` with permission boundary tests
-- `decision-log/ADR-XXXX.md` for storage and retention choices
-
-## Risk and compliance
-- Data confidentiality (client privilege)
-- Retention and legal hold policies
-- Audit trails for all access and edits
-
-## Acceptance criteria examples
-- Every document access is logged with user, timestamp, and reason.
-- Retention rules can be configured per case type.
-- Access is role-based and least-privilege by default.
-
-## Recommended outputs
-- Secure storage and audit module
-- Role-based access matrix
-- Case timeline dashboard
+# Flow: Lawyer (legal practice)
+
+## Goal
+Build a system to manage cases, documents, deadlines, and client communication with strong audit trails.
+
+## Discovery prompts
+- What case types are supported (civil, criminal, corporate)?
+- What jurisdictions and compliance rules apply?
+- What data is sensitive or privileged?
+- Who are the actors (partners, associates, paralegals, clients)?
+- What are the legal deadlines and escalation rules?
+
+## Required artifacts
+- `requirement.md` with scope and compliance constraints
+- `functional-spec.md` including case lifecycle and document review flows
+- `technical-spec.md` detailing access control and audit logging
+- `docs/ARCHITECTURE.md` with secure storage and encryption at rest
+- `test-plan.md` with permission boundary tests
+- `decision-log/ADR-XXXX.md` for storage and retention choices
+
+## Risk and compliance
+- Data confidentiality (client privilege)
+- Retention and legal hold policies
+- Audit trails for all access and edits
+
+## Acceptance criteria examples
+- Every document access is logged with user, timestamp, and reason.
+- Retention rules can be configured per case type.
+- Access is role-based and least-privilege by default.
+
+## Recommended outputs
+- Secure storage and audit module
+- Role-based access matrix
+- Case timeline dashboard
+

package/flows/PROGRAMMER.md

@@ -1,33 +1,34 @@
-# Flow: Programmer
-
-## Goal
-Implement a feature or system change with clean code, tests, and documentation.
-
-## Discovery prompts
-- What is the feature and who needs it?
-- What are the acceptance criteria?
-- What existing code areas are impacted?
-- What constraints exist (performance, security, compatibility)?
-- What is the expected rollout strategy?
-
-## Required artifacts
-- `requirement.md` with scope and constraints
-- `functional-spec.md` for behavior and edge cases
-- `technical-spec.md` for design and dependencies
-- `architecture.md` for component-level impact
-- `test-plan.md` for coverage and regression
-
-## Risk and compliance
-- Regression risk on critical flows
-- Backward compatibility
-- Operational impacts
-
-## Acceptance criteria examples
-- Feature works in primary and edge scenarios.
-- Tests cover new logic and critical regressions.
-- Documentation updated for users and developers.
-
-## Recommended outputs
-- Implementation plan
-- Code review checklist
-- Rollout plan
+# Flow: Programmer
+
+## Goal
+Implement a feature or system change with clean code, tests, and documentation.
+
+## Discovery prompts
+- What is the feature and who needs it?
+- What are the acceptance criteria?
+- What existing code areas are impacted?
+- What constraints exist (performance, security, compatibility)?
+- What is the expected rollout strategy?
+
+## Required artifacts
+- `requirement.md` with scope and constraints
+- `functional-spec.md` for behavior and edge cases
+- `technical-spec.md` for design and dependencies
+- `docs/ARCHITECTURE.md` for component-level impact
+- `test-plan.md` for coverage and regression
+
+## Risk and compliance
+- Regression risk on critical flows
+- Backward compatibility
+- Operational impacts
+
+## Acceptance criteria examples
+- Feature works in primary and edge scenarios.
+- Tests cover new logic and critical regressions.
+- Documentation updated for users and developers.
+
+## Recommended outputs
+- Implementation plan
+- Code review checklist
+- Rollout plan
+

package/flows/RETAIL_STORE.md

@@ -1,33 +1,34 @@
-# 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
+# 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
+- `docs/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

@@ -1,33 +1,34 @@
-# 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
+# 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
+- `docs/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

@@ -1,33 +1,34 @@
-# 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
+# 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
+- `docs/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

@@ -1,33 +1,34 @@
-# 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
+# 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
+- `docs/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

@@ -1,33 +1,34 @@
-# 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
+# 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
+- `docs/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
+