specsmd 0.0.1

package/flows/aidlc/templates/inception/requirements-template.md

@@ -0,0 +1,144 @@
+# Requirements Template
+
+Use this template when documenting requirements for an intent.
+
+---
+
+## Frontmatter
+
+```yaml
+---
+intent: {intent-name}
+phase: inception
+status: draft|in-progress|complete
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+```
+
+Note: All naming is derived from folder names. No prefix field needed.
+
+---
+
+## Content
+
+```markdown
+# Requirements: {Intent Name}
+
+## Intent Overview
+
+{High-level description of what this intent aims to achieve}
+
+## Business Goals
+
+| Goal | Success Metric | Priority |
+|------|----------------|----------|
+| {Goal 1} | {How to measure success} | Must |
+| {Goal 2} | {How to measure success} | Should |
+
+---
+
+## Functional Requirements
+
+### FR-1: {Requirement Title}
+- **Description**: {What the system must do}
+- **Acceptance Criteria**: {Measurable conditions for success}
+- **Priority**: Must/Should/Could
+- **Related Stories**: {Story IDs when defined}
+
+### FR-2: {Requirement Title}
+- **Description**: {What the system must do}
+- **Acceptance Criteria**: {Measurable conditions for success}
+- **Priority**: Must/Should/Could
+- **Related Stories**: {Story IDs when defined}
+
+---
+
+## Non-Functional Requirements
+
+### Performance
+| Requirement | Metric | Target |
+|-------------|--------|--------|
+| Response Time | p95 latency | < 200ms |
+| Throughput | Requests/second | > 1000 |
+
+### Scalability
+| Requirement | Metric | Target |
+|-------------|--------|--------|
+| Concurrent Users | Active sessions | 10,000 |
+| Data Volume | Records | 10M+ |
+
+### Security
+| Requirement | Standard | Notes |
+|-------------|----------|-------|
+| Authentication | OAuth 2.0 / JWT | {details} |
+| Authorization | RBAC | {details} |
+| Data Protection | AES-256 | {details} |
+
+### Reliability
+| Requirement | Metric | Target |
+|-------------|--------|--------|
+| Availability | Uptime | 99.9% |
+| Recovery | RTO | < 1 hour |
+
+### Compliance
+| Requirement | Standard | Notes |
+|-------------|----------|-------|
+| {Regulation} | {Standard} | {details} |
+
+---
+
+## Constraints
+
+### Technical Constraints
+
+**Project-wide standards**: Required standards will be loaded from memory-bank standards folder by Construction Agent
+
+**Intent-specific constraints** (only list constraints unique to this feature):
+- {Constraint specific to this intent, not covered by standards}
+
+### Business Constraints
+- {Constraint 1: e.g., budget limitation}
+- {Constraint 2: e.g., timeline requirement}
+
+---
+
+## Assumptions
+
+| Assumption | Risk if Invalid | Mitigation |
+|------------|-----------------|------------|
+| {Assumption 1} | {What happens if wrong} | {How to mitigate} |
+| {Assumption 2} | {What happens if wrong} | {How to mitigate} |
+
+---
+
+## Open Questions
+
+| Question | Owner | Due Date | Resolution |
+|----------|-------|----------|------------|
+| {Question 1} | {Who} | {When} | {Pending/Resolved} |
+```
+
+---
+
+## Priority Definitions
+
+| Priority | Meaning |
+|----------|---------|
+| **Must** | Required for MVP, system unusable without |
+| **Should** | Important, significant value but not blocking |
+| **Could** | Nice to have, enhances experience |
+| **Won't** | Out of scope for this intent |
+
+---
+
+## Requirement Quality Checklist
+
+Before marking requirements complete, verify:
+
+- [ ] All requirements are testable (measurable, not vague)
+- [ ] Acceptance criteria are binary (pass/fail)
+- [ ] NFRs have specific metrics and targets
+- [ ] Dependencies are identified
+- [ ] Constraints are documented
+- [ ] Assumptions are stated and risks assessed

package/flows/aidlc/templates/inception/stories-template.md

@@ -0,0 +1,38 @@
+---
+intent: {intent-name}
+phase: inception
+status: stories-created
+updated: {date}
+---
+
+# {Intent Name} - Stories
+
+## User Stories
+
+### Story-1: {Title}
+
+**As a** {user type}
+**I want** {goal}
+**So that** {benefit}
+
+**Acceptance Criteria**:
+
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+
+**Priority**: High/Medium/Low
+**Estimate**: {T-shirt size: S/M/L/XL}
+
+### Story-2: {Title}
+
+...
+
+## Technical Stories
+
+### Tech-Story-1: {Title}
+
+**Description**: {What needs to be done technically}
+**Rationale**: {Why this is needed}
+**Acceptance Criteria**:
+
+- [ ] {Criterion}

package/flows/aidlc/templates/inception/story-template.md

@@ -0,0 +1,147 @@
+# Story Template
+
+Use this template when creating individual story files during story creation.
+
+---
+
+## Frontmatter
+
+```yaml
+---
+id: {intent-name}-story-{n}
+unit: {unit-name}
+intent: {intent-name}
+status: draft
+priority: must|should|could
+created: {YYYY-MM-DD}
+assigned_bolt: null
+implemented: false
+---
+```
+
+---
+
+## Content
+
+```markdown
+# Story: {intent-name}-story-{n}
+
+## User Story
+
+**As a** {user role}
+**I want** {goal/action}
+**So that** {benefit/reason}
+
+## Acceptance Criteria
+
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+- [ ] **Given** {precondition}, **When** {action}, **Then** {expected outcome}
+
+## Technical Notes
+
+{Implementation hints, constraints, or considerations}
+
+## Dependencies
+
+### Requires
+- {Other stories this depends on, or "None"}
+
+### Enables
+- {Stories that depend on this, or "None"}
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| {edge case 1} | {behavior} |
+| {edge case 2} | {behavior} |
+
+## Out of Scope
+
+- {What this story does NOT cover}
+```
+
+---
+
+## Priority Levels
+
+| Priority | Meaning | Criteria |
+|----------|---------|----------|
+| `must` | Required for MVP | System unusable without this |
+| `should` | Important | Significant value, not blocking |
+| `could` | Nice to have | Enhances experience |
+
+---
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `draft` | Story written, needs review |
+| `ready` | Reviewed, ready for bolt |
+| `in-progress` | Being implemented in a bolt |
+| `implemented` | Code complete |
+| `tested` | Tests passing |
+| `done` | All acceptance criteria met |
+
+---
+
+## Example
+
+```yaml
+---
+id: user-authentication-story-1
+unit: auth-service
+intent: user-authentication
+status: ready
+priority: must
+created: 2024-12-05
+assigned_bolt: bolt-auth-service-1
+implemented: false
+---
+```
+
+```markdown
+# Story: user-authentication-story-1
+
+## User Story
+
+**As a** new user
+**I want** to register with my email and password
+**So that** I can access the application
+
+## Acceptance Criteria
+
+- [ ] **Given** I am on the registration page, **When** I enter valid email and password, **Then** my account is created and I receive a confirmation email
+- [ ] **Given** I enter an email that already exists, **When** I submit registration, **Then** I see an error message "Email already registered"
+- [ ] **Given** I enter a password less than 8 characters, **When** I submit, **Then** I see validation error
+
+## Technical Notes
+
+- Password must be hashed with bcrypt (cost factor 12)
+- Email validation should use RFC 5322 compliant regex
+- Rate limit registration to 5 attempts per IP per hour
+
+## Dependencies
+
+### Requires
+- None (first story)
+
+### Enables
+- story-2 (User login)
+- story-3 (Email verification)
+
+## Edge Cases
+
+| Scenario | Expected Behavior |
+|----------|-------------------|
+| SQL injection in email | Safely escaped, validation fails |
+| Very long email (255+ chars) | Validation error |
+| Unicode in password | Allowed, properly encoded |
+
+## Out of Scope
+
+- Social login (OAuth) - separate story
+- Password reset - separate story
+```

package/flows/aidlc/templates/inception/system-context-template.md

@@ -0,0 +1,29 @@
+---
+intent: {intent-name}
+phase: inception
+status: context-defined
+updated: {date}
+---
+
+# {Intent Name} - System Context
+
+## System Overview
+
+{High-level description of what we are building}
+
+## Context Diagram
+
+{Mermaid diagram showing System, Users, and External Systems}
+
+## External Integrations
+
+- **System A**: {Purpose of integration}
+- **System B**: {Purpose of integration}
+
+## High-Level Constraints
+
+- {e.g., Must run on AWS, Must use existing Auth provider}
+
+## Key NFR Goals
+
+- {High-level performance/security goals to guide construction}

package/flows/aidlc/templates/inception/unit-brief-template.md

@@ -0,0 +1,177 @@
+# Unit Brief Template
+
+Use this template when creating unit briefs during decomposition. This is the **critical input for Construction**.
+
+---
+
+## Frontmatter
+
+```yaml
+---
+unit: {unit-name}
+intent: {intent-name}
+phase: inception
+status: draft|ready
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+```
+
+Note: Story naming uses the story title (e.g., `001-user-signup.md`). No prefix field needed.
+
+---
+
+## Content
+
+```markdown
+# Unit Brief: {Unit Name}
+
+## Purpose
+
+{Clear, concise statement of what this unit does and why it exists}
+
+## Scope
+
+### In Scope
+- {What this unit IS responsible for}
+- {What this unit IS responsible for}
+
+### Out of Scope
+- {What this unit is NOT responsible for}
+- {What other units handle}
+
+---
+
+## Assigned Requirements
+
+**These FRs from the intent are assigned to this unit. Stories will be created from these.**
+
+| FR | Requirement | Priority |
+|----|-------------|----------|
+| FR-{n} | {description from intent requirements.md} | Must/Should/Could |
+
+---
+
+## Domain Concepts
+
+### Key Entities
+| Entity | Description | Attributes |
+|--------|-------------|------------|
+| {Entity 1} | {What it represents} | {Key properties} |
+| {Entity 2} | {What it represents} | {Key properties} |
+
+### Key Operations
+| Operation | Description | Inputs | Outputs |
+|-----------|-------------|--------|---------|
+| {Operation 1} | {What it does} | {Input data} | {Output data} |
+| {Operation 2} | {What it does} | {Input data} | {Output data} |
+
+---
+
+## Story Summary
+
+| Metric | Count |
+|--------|-------|
+| Total Stories | {n} |
+| Must Have | {n} |
+| Should Have | {n} |
+| Could Have | {n} |
+
+### Stories
+
+| Story ID | Title | Priority | Status |
+|----------|-------|----------|--------|
+| {story-1} | {Title} | Must | Planned |
+| {story-2} | {Title} | Should | Planned |
+
+---
+
+## Dependencies
+
+### Depends On
+| Unit | Reason |
+|------|--------|
+| {unit-name} | {Why this dependency exists} |
+
+### Depended By
+| Unit | Reason |
+|------|--------|
+| {unit-name} | {Why they depend on this} |
+
+### External Dependencies
+| System | Purpose | Risk |
+|--------|---------|------|
+| {External system} | {Why needed} | {Risk level} |
+
+---
+
+## Technical Context
+
+### Suggested Technology
+{Recommendations based on tech stack standards}
+
+### Integration Points
+| Integration | Type | Protocol |
+|-------------|------|----------|
+| {System/Unit} | API/Event/DB | REST/GraphQL/Kafka |
+
+### Data Storage
+| Data | Type | Volume | Retention |
+|------|------|--------|-----------|
+| {Data type} | SQL/NoSQL/Cache | {Volume} | {Retention} |
+
+---
+
+## Constraints
+
+- {Technical constraint specific to this unit}
+- {Business constraint specific to this unit}
+
+---
+
+## Success Criteria
+
+### Functional
+- [ ] {Criterion 1: What must work}
+- [ ] {Criterion 2: What must work}
+
+### Non-Functional
+- [ ] {Performance target}
+- [ ] {Security requirement}
+
+### Quality
+- [ ] Code coverage > 80%
+- [ ] All acceptance criteria met
+- [ ] Code reviewed and approved
+
+---
+
+## Bolt Suggestions
+
+Based on stories and complexity:
+
+| Bolt | Type | Stories | Objective |
+|------|------|---------|-----------|
+| bolt-{unit}-1 | DDD | S1, S2 | Core entities |
+| bolt-{unit}-2 | DDD | S3, S4 | API layer |
+
+---
+
+## Notes
+
+{Any additional context, risks, or considerations for Construction}
+```
+
+---
+
+## Quality Checklist
+
+Before marking unit brief as ready:
+
+- [ ] Purpose is clear and specific
+- [ ] Scope boundaries are defined
+- [ ] Key entities identified
+- [ ] Stories assigned to this unit
+- [ ] Dependencies mapped
+- [ ] Success criteria are measurable
+- [ ] Bolt suggestions provided

package/flows/aidlc/templates/inception/units-template.md

@@ -0,0 +1,52 @@
+---
+intent: {intent-name}
+phase: inception
+status: units-decomposed
+updated: {date}
+---
+
+# {Intent Name} - Unit Decomposition
+
+## Units Overview
+
+This intent decomposes into {N} units of work:
+
+### Unit 1: {unit-name}
+
+**Description**: {What this unit does}
+
+**Stories**:
+
+- Story-1: {Title}
+- Story-3: {Title}
+
+**Deliverables**:
+
+- {Specific artifacts this unit produces}
+
+**Dependencies**:
+
+- Depends on: {Other units}
+- Depended by: {Units that need this}
+
+**Estimated Complexity**: S/M/L/XL
+
+### Unit 2: {unit-name}
+
+...
+
+## Unit Dependency Graph
+
+```text
+[Unit A] ──> [Unit B] ──> [Unit D]
+   │            │
+   └────> [Unit C] ──┘
+```
+
+## Execution Order
+
+Based on dependencies:
+
+1. Day 1-2: Unit A (foundation)
+2. Day 2-4: Unit B, Unit C (parallel)
+3. Day 5-6: Unit D (integration)