@delete101020/aidlc 4.0.0

package/dist/templates/sdlc/artifacts/implement.md

@@ -0,0 +1,70 @@
+# Implementation Summary — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Author:** Developer
+**Branch:** `feature/$EPIC_ID-<slug>`
+**Status:** Draft
+**Created:** `$DATE`
+
+---
+
+## 1. Branch & PR
+
+| Item   | Value |
+|--------|-------|
+| Branch | `feature/$EPIC_ID-<slug>` |
+| PR     | *(link once opened)* |
+| Base   | `main` |
+
+## 2. Files Changed
+
+| File | Type | Description |
+|------|------|-------------|
+| `src/...` | Add | … |
+| `src/...` | Modify | … |
+
+## 3. Implementation Notes
+
+> *Key decisions made during implementation. Reference design doc sections where relevant.*
+
+### Deviations from Tech Design
+
+> *List any places where implementation diverged from `TECH-DESIGN.md` and why.*
+
+None.
+
+## 4. Unit Tests (TDD — written before the code)
+
+> Tests were authored first (red), then the implementation made them pass (green).
+
+| Test file | Cases (`$EPIC_ID-UT*`) | Type (happy / error / edge) |
+|-----------|------------------------|------------------------------|
+| `src/__tests__/...` | | |
+
+## 5. Whole-Project Coverage (re-run after implementation)
+
+> Required. Coverage is re-run across the **entire** project after the code is
+> green — not just the changed files. If the project has no coverage tooling,
+> state that here instead of leaving it blank.
+
+| Item | Value |
+|------|-------|
+| Coverage command | `<project coverage command>` |
+| Total coverage | `<N>%` (lines) / `<N>%` (branches) |
+| Delta vs base | `<+/- N>%` |
+| Meets target | `<yes / no>` (target ≥ 80%) |
+
+## 6. Pre-PR Checklist
+
+- [ ] Unit tests written **before** the implementation (TDD)
+- [ ] Lint passes (`npm run lint`)
+- [ ] Type-check passes (`npm run typecheck`)
+- [ ] Full unit-test suite passes (`npm test`)
+- [ ] Whole-project coverage re-run and recorded in §5
+- [ ] No new console errors in dev mode
+- [ ] PR body references epic key `$EPIC_ID`
+- [ ] Reviewer assigned
+
+## 7. Known Limitations / Follow-ups
+
+- …

package/dist/templates/sdlc/artifacts/implement.web-react.md

@@ -0,0 +1,109 @@
+# Implementation Summary — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Author:** Developer
+**Branch:** `feature/$EPIC_ID-<slug>`
+**Status:** Draft
+**Created:** `$DATE`
+**Stack:** React
+
+---
+
+## 1. Branch & PR
+
+| Item   | Value |
+|--------|-------|
+| Branch | `feature/$EPIC_ID-<slug>` |
+| PR     | *(link once opened)* |
+| Base   | `main` |
+
+## 2. Files Changed
+
+| File | Type | Description |
+|------|------|-------------|
+| `src/components/...` | Add | … |
+| `src/hooks/...` | Add | … |
+| `src/...` | Modify | … |
+
+## 3. Component & Hook Design
+
+| Concern | Decision |
+|---------|----------|
+| New components | *(name, props contract, where rendered)* |
+| Custom hooks | *(name, inputs/outputs, what side-effects they own)* |
+| State | *(useState / useReducer / context / external store — and why)* |
+| Data fetching | *(query lib cache key, suspense vs. effect, invalidation)* |
+| Memoization | *(any `useMemo`/`useCallback`/`memo` and the cost they avoid)* |
+
+### Re-render / performance notes
+
+> *Call out anything done to avoid wasteful re-renders (stable identities,
+> key choices, list virtualization). State "none needed" if N/A.*
+
+### Deviations from Tech Design
+
+> *List any places where implementation diverged from `TECH-DESIGN.md` and why.*
+
+None.
+
+## 4. Accessibility
+
+- [ ] Interactive elements are real buttons/links (or have correct `role`)
+- [ ] Keyboard navigable, visible focus states, no keyboard traps
+- [ ] Labels/`aria-*` on inputs; errors announced
+- [ ] Color contrast meets WCAG AA
+- [ ] Respects `prefers-reduced-motion`
+
+{{#if backend}}
+## 4b. API Integration
+
+| Endpoint | Method | Request → Response shape | Query/mutation key | Error states |
+|----------|--------|--------------------------|--------------------|--------------|
+| `/api/...` | GET | … → … | `['...']` | loading / empty / error |
+
+- [ ] Loading, empty, and error states rendered for every async call
+- [ ] Response types shared with (or matched to) the backend
+{{/if}}
+
+## 5. Tests (TDD — React Testing Library)
+
+> Tests authored first (red), then the implementation made them pass (green).
+> Query by **role/label/text** (what the user sees), not by test-id or
+> internal component state. Use `userEvent` for interactions.
+
+| Test file | Cases (`$EPIC_ID-UT*`) | Type (happy / error / edge) |
+|-----------|------------------------|------------------------------|
+| `src/components/__tests__/...` | | |
+| `src/hooks/__tests__/...` | | |
+
+- [ ] Hooks tested via a component or `renderHook`
+- [ ] Async UI asserted with `findBy*` / `waitFor` (no arbitrary timeouts)
+
+## 6. Whole-Project Coverage (re-run after implementation)
+
+> Required. Coverage is re-run across the **entire** project after the code is
+> green — not just the changed files. If the project has no coverage tooling,
+> state that here instead of leaving it blank.
+
+| Item | Value |
+|------|-------|
+| Coverage command | `<project coverage command>` |
+| Total coverage | `<N>%` (lines) / `<N>%` (branches) |
+| Delta vs base | `<+/- N>%` |
+| Meets target | `<yes / no>` (target ≥ 80%) |
+
+## 7. Pre-PR Checklist
+
+- [ ] Component/hook tests written **before** the implementation (TDD)
+- [ ] Lint passes (`npm run lint`)
+- [ ] Type-check passes (`npm run typecheck`)
+- [ ] Full test suite passes (`npm test`)
+- [ ] Whole-project coverage re-run and recorded in §6
+- [ ] No new console errors / React warnings (keys, act(), missing deps)
+- [ ] Accessibility checklist (§4) reviewed
+- [ ] PR body references epic key `$EPIC_ID`
+- [ ] Reviewer assigned
+
+## 8. Known Limitations / Follow-ups
+
+- …

package/dist/templates/sdlc/artifacts/implement.web.md

@@ -0,0 +1,99 @@
+# Implementation Summary — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Author:** Developer
+**Branch:** `feature/$EPIC_ID-<slug>`
+**Status:** Draft
+**Created:** `$DATE`
+
+---
+
+## 1. Branch & PR
+
+| Item   | Value |
+|--------|-------|
+| Branch | `feature/$EPIC_ID-<slug>` |
+| PR     | *(link once opened)* |
+| Base   | `main` |
+
+## 2. Files Changed
+
+| File | Type | Description |
+|------|------|-------------|
+| `src/components/...` | Add | … |
+| `src/...` | Modify | … |
+
+## 3. UI / Component Notes
+
+> *Key decisions: component breakdown, state management, routing, data fetching.*
+
+| Concern | Decision |
+|---------|----------|
+| Component structure | *(container vs. presentational, where state lives)* |
+| State / data fetching | *(local state, store, query cache)* |
+| Routing | *(new routes / params added)* |
+
+### Deviations from Tech Design
+
+> *List any places where implementation diverged from `TECH-DESIGN.md` and why.*
+
+None.
+
+## 4. Accessibility & Responsiveness
+
+- [ ] Keyboard navigable (tab order, focus states, no keyboard traps)
+- [ ] Semantic HTML / ARIA roles where needed
+- [ ] Color contrast meets WCAG AA
+- [ ] Works at mobile / tablet / desktop breakpoints
+- [ ] Respects `prefers-reduced-motion`
+
+{{#if backend}}
+## 4b. API Integration
+
+> This project also has a backend. Record the contract the UI depends on.
+
+| Endpoint | Method | Request → Response shape | Error states handled |
+|----------|--------|--------------------------|----------------------|
+| `/api/...` | GET | … → … | loading / empty / error |
+
+- [ ] Loading, empty, and error states rendered for every async call
+- [ ] Request/response types shared with (or matched to) the backend
+{{/if}}
+
+## 5. Unit / Component Tests (TDD — written before the code)
+
+> Tests authored first (red), then the implementation made them pass (green).
+> Prefer testing behavior through the rendered DOM over implementation details.
+
+| Test file | Cases (`$EPIC_ID-UT*`) | Type (happy / error / edge) |
+|-----------|------------------------|------------------------------|
+| `src/components/__tests__/...` | | |
+
+## 6. Whole-Project Coverage (re-run after implementation)
+
+> Required. Coverage is re-run across the **entire** project after the code is
+> green — not just the changed files. If the project has no coverage tooling,
+> state that here instead of leaving it blank.
+
+| Item | Value |
+|------|-------|
+| Coverage command | `<project coverage command>` |
+| Total coverage | `<N>%` (lines) / `<N>%` (branches) |
+| Delta vs base | `<+/- N>%` |
+| Meets target | `<yes / no>` (target ≥ 80%) |
+
+## 7. Pre-PR Checklist
+
+- [ ] Component/unit tests written **before** the implementation (TDD)
+- [ ] Lint passes (`npm run lint`)
+- [ ] Type-check passes (`npm run typecheck`)
+- [ ] Full test suite passes (`npm test`)
+- [ ] Whole-project coverage re-run and recorded in §6
+- [ ] No new console errors / warnings in dev mode
+- [ ] Accessibility checklist (§4) reviewed
+- [ ] PR body references epic key `$EPIC_ID`
+- [ ] Reviewer assigned
+
+## 8. Known Limitations / Follow-ups
+
+- …

package/dist/templates/sdlc/artifacts/plan.md

@@ -0,0 +1,97 @@
+# PRD — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Author:** Product Owner
+**Status:** Draft
+**Created:** `$DATE`
+
+---
+
+## 0. Discovery decisions
+
+> *Only when the discovery gate ran. One line per resolved question → the chosen answer
+> (including any "Decide for me" defaults that stood). Downstream phases read confirmed
+> scope / approach from here. Omit this section for a small, clear epic that skipped the gate.*
+
+| # | Question | Decision |
+|---|----------|----------|
+| 1 |          |          |
+
+## 1. Problem Statement
+
+> *Describe the user or business problem this epic solves. Why does it exist?*
+
+## 2. Goals
+
+- [ ] Goal 1
+- [ ] Goal 2
+- [ ] Goal 3
+
+## 3. Non-Goals
+
+- Out of scope: …
+- Will not address: …
+
+## 4. Affected Areas
+
+> *Existing product surfaces, modules, user segments, or flows this epic
+> touches — including the ones it does NOT change but could regress. Helps
+> reviewers and QA gauge blast radius before any code is written.*
+
+| Area / Surface | Kind (screen / flow / service / data / integration) | Impact (new / modified / deprecated) | Notes |
+|----------------|------------------------------------------------------|--------------------------------------|-------|
+|                |                                                      |                                      |       |
+
+## 5. User Stories
+
+| As a… | I want to… | So that… |
+|--------|------------|----------|
+| user   |            |          |
+
+## 6. Functional Requirements
+
+### FR-01: [Feature name]
+
+**Description:** …
+**Acceptance Criteria:**
+- [ ] AC-01: …
+- [ ] AC-02: …
+
+### FR-02: [Feature name]
+
+**Description:** …
+**Acceptance Criteria:**
+- [ ] AC-01: …
+
+## 7. Non-Functional Requirements
+
+| Category       | Requirement                        |
+|----------------|------------------------------------|
+| Performance    | p95 response < 500 ms              |
+| Accessibility  | WCAG 2.1 AA                        |
+| Security       | No PII logged                      |
+| Compatibility  | iOS 16+, Android 12+               |
+
+## 8. Design & References
+
+- Figma: *(link)*
+- Jira: *(ticket)*
+- Related docs: *(links)*
+
+## 9. Metrics / Success Criteria
+
+| Metric           | Baseline | Target |
+|------------------|----------|--------|
+| Conversion rate  | —        | —      |
+| Error rate       | —        | < 1%   |
+
+## 10. Open Questions
+
+- [ ] Q1: …
+- [ ] Q2: …
+
+## 11. Revision History
+
+| Date | Author | Change |
+|------|--------|--------|
+|      |        | Initial draft |

package/dist/templates/sdlc/artifacts/prototype.md

@@ -0,0 +1,141 @@
+# UI Prototype — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Designer:** Designer Agent
+**Status:** Draft → Awaiting Review
+**Created:** `$DATE`
+
+---
+
+## Design Method Chosen
+
+- **Method:** [Claude Artifacts / Figma / shadcn/ui / Project Design System / Lo-fi Wireframe]
+- **Why this method:** [Brief rationale — speed vs. fidelity, project needs, team preferences]
+
+## Options Generated
+
+### Option 1: [Title / Focus]
+
+**Intent:**
+> [What makes this option distinct? E.g., "Compact layout with sidebar navigation for power users"]
+
+**Layout:**
+- Structure: [Single-column / multi-column / sidebar / top nav?]
+- Grid / spacing: [e.g., 12-column grid, 8px baseline]
+- Breakpoints: [Mobile / tablet / desktop breakpoint targets]
+
+**Key Decisions:**
+- Primary action: [What gets emphasis and where?]
+- Information hierarchy: [What's visible first? What's secondary / hidden?]
+- Component patterns: [Which design system components? Any custom variations?]
+- Color / contrast: [Palette, accessibility level (AA / AAA?), dark mode?]
+
+**Tradeoffs:**
+- ✓ Strengths: [What works well in this option]
+- ✗ Weaknesses: [What's uncertain or risky]
+
+**Responsive notes:** [Mobile behavior, touch targets ≥48px?, landscape mode?]
+
+---
+
+### Option 2: [Title / Focus]
+
+[Repeat structure above]
+
+---
+
+### Option 3 (if generated): [Title / Focus]
+
+[Repeat structure above]
+
+---
+
+## Chosen Option
+
+**Selected:** Option [N] — [Title / Focus]
+
+**Why the user picked this one:**
+> [Feedback from the discovery gate — what resonated with the team?]
+
+**Any adjustments requested:**
+- [Refinements to explore in the Design phase]
+- [Questions the Tech Lead should weigh in on]
+
+---
+
+## Design Details (Chosen Option)
+
+### Layout & Navigation
+
+[Structure, grid system, key screens/flows, navigation pattern]
+
+### Components
+
+| Pattern | Component Used | Customization |
+|---------|----------------|---------------|
+| [Button] | [shadcn Button / Figma component / custom] | [None / minor / significant] |
+| [Form input] | [shadcn Input / custom] | [None / minor / significant] |
+| [Modal] | [shadcn Dialog / custom] | [None / minor / significant] |
+
+### Accessibility
+
+- **Color contrast:** WCAG [AA / AAA]
+- **Keyboard navigation:** [Fully navigable / mostly / needs work]
+- **Screen reader:** [Semantic HTML / ARIA labels / needs work]
+- **Focus indicators:** [Clear / subtle / needs improvement]
+
+### Responsive Behavior
+
+| Screen | Layout | Notes |
+|--------|--------|-------|
+| Mobile (< 640px) | [Single-column / stacked nav] | [Touch targets, no hover-only] |
+| Tablet (640–1024px) | [2-column / side nav] | [Optimized spacing] |
+| Desktop (> 1024px) | [Full layout] | [Optimal reading width, pointer interactions] |
+
+### Dark Mode
+
+- **Status:** [Supported / not applicable / TBD]
+- **Approach:** [CSS variables / Tailwind dark: modifier / manual] 
+- **Key color changes:** [List any that differ from light mode]
+
+---
+
+## Next Steps for Design Phase
+
+- [ ] Validate responsive behavior on actual devices (mobile / tablet / desktop)
+- [ ] Confirm all text is final or use placeholder labels (Lorem ipsum OK?)
+- [ ] Check that design system components are available in the project
+- [ ] Any performance concerns (animations, bundle size)?
+- [ ] Questions for the Tech Lead:
+  - [What's the existing pattern for X in this project?]
+  - [Can we use Y library or do we need Z instead?]
+  - [How should error states / loading / empty states look?]
+
+---
+
+## Artifacts
+
+- **`PROTOTYPE-option1.html`** (or `.figma-link.md` / `.excalidraw.md`)
+  - [Brief description of what this file contains]
+
+- **`PROTOTYPE-option2.html`**
+  - [Brief description]
+
+- **`PROTOTYPE-option3.html`** (if applicable)
+  - [Brief description]
+
+---
+
+## Review Checklist
+
+- [ ] ≥2 distinct UI options generated
+- [ ] Each option documented (layout, components, accessibility)
+- [ ] Chosen option rationale recorded
+- [ ] All design decisions tied back to PRD (esp. Discovery decisions)
+- [ ] Responsive behavior addressed
+- [ ] Accessibility (color contrast, keyboard nav) verified
+- [ ] Ready for Design phase to validate and refine against technical constraints
+
+---
+
+**Next phase:** /design $EPIC_ID — Design phase reads this prototype and writes TECH-DESIGN.md

package/dist/templates/sdlc/artifacts/test-cases.md

@@ -0,0 +1,47 @@
+# Test Cases — {{EPIC_ID}}
+
+> Concrete, executable test cases derived from the approved Test Plan.
+> Written by QA while Implementation is in flight (parallel track).
+
+## Sources
+
+- Test Plan: `TEST-PLAN.md`
+- PRD acceptance criteria: `PRD.md`
+
+## Test case catalogue
+
+### Unit / IT cases (engineering owns the code)
+
+| ID | Description | Type | Linked AC | Notes |
+|----|-------------|------|-----------|-------|
+| UT-1 |  | unit |  |  |
+| IT-1 |  | integration |  |  |
+
+### UI / E2E cases
+
+| ID | Steps | Expected | Linked AC | Data / fixtures |
+|----|-------|----------|-----------|-----------------|
+| E2E-1 |  |  |  |  |
+
+### Negative / edge cases
+
+| ID | Setup | Action | Expected error | Linked AC |
+|----|-------|--------|----------------|-----------|
+| NEG-1 |  |  |  |  |
+
+## Data + fixtures
+
+- Test users / accounts:
+- Mock services:
+- Seed data:
+
+## Out of scope
+
+- Cases deferred to a later epic — list explicitly so coverage gaps are
+  visible at review time.
+
+## Hand-off
+
+- Execute Test phase consumes this artifact to drive the test run.
+- Any case that can't be executed without code changes belongs in
+  Implementation, not here.

package/dist/templates/sdlc/artifacts/test-plan.md

@@ -0,0 +1,100 @@
+# Test Plan — [Epic Title]
+
+**Epic ID:** `$EPIC_ID`
+**Author:** QA
+**Status:** Draft
+**Created:** `$DATE`
+
+---
+
+## 1. Scope
+
+> *What is being tested? What is explicitly out of scope?*
+
+**In scope:**
+- Feature A
+- Integration with B
+
+**Out of scope:**
+- Legacy flow X
+
+## 2. Test Strategy
+
+| Type             | Tool / Approach          | Owner |
+|------------------|--------------------------|-------|
+| Unit tests       | Jest / XCTest            | Dev   |
+| Integration      | API contract tests       | QA    |
+| UI / E2E         | Detox / Playwright       | QA    |
+| Performance      | k6 / Instruments         | QA    |
+| Accessibility    | axe-core / VoiceOver     | QA    |
+
+## 3. Test Cases
+
+### TC-01: [Happy path description]
+
+**Preconditions:** …
+**Steps:**
+1. …
+2. …
+3. …
+**Expected result:** …
+**AC covered:** AC-01
+
+---
+
+### TC-02: [Error / edge case description]
+
+**Preconditions:** …
+**Steps:**
+1. …
+**Expected result:** …
+**AC covered:** AC-02
+
+---
+
+### TC-03: [Boundary condition]
+
+**Preconditions:** …
+**Steps:**
+1. …
+**Expected result:** …
+
+## 4. Unit Test Coverage Requirements
+
+| Module | Target coverage | Notes |
+|--------|----------------|-------|
+| `src/` | ≥ 80%          |       |
+
+## 5. Device / Browser Matrix
+
+| Platform   | Version | Priority |
+|------------|---------|----------|
+| iOS        | 17      | P1       |
+| iOS        | 16      | P2       |
+| Android    | 14      | P1       |
+| Android    | 12      | P2       |
+| Chrome     | latest  | P1       |
+| Safari     | latest  | P1       |
+
+## 6. Performance Benchmarks
+
+| Scenario     | Threshold       |
+|--------------|----------------|
+| API p95      | < 500 ms        |
+| First render | < 1 s           |
+| Cold start   | < 2 s           |
+
+## 7. Regression Checklist
+
+> *Existing flows that must still work after this change.*
+
+- [ ] Login / logout
+- [ ] …
+
+## 8. Sign-off Criteria
+
+- [ ] All TC-xx pass
+- [ ] Unit coverage ≥ target
+- [ ] No P1 open bugs
+- [ ] Performance benchmarks met
+- [ ] QA sign-off

package/dist/templates/sdlc/artifacts/unit-test.md

@@ -0,0 +1,32 @@
+# Unit Test Summary — {{EPIC_KEY}}
+
+> Produced by the `unit-test` phase. Records the unit tests added on the
+> feature branch and how they map back to the test plan.
+
+## Branch
+`feature/{{EPIC_KEY}}-<slug>`
+
+## Tests added
+| Test ID | File | What it verifies | Type (happy / error / edge) |
+|---------|------|------------------|------------------------------|
+| {{EPIC_KEY}}-UT01 | | | |
+
+## Coverage vs TEST-PLAN
+- [ ] Every `{{EPIC_KEY}}-UT*` case in `TEST-PLAN.md` has a corresponding test
+- [ ] Happy path covered
+- [ ] Error / failure paths from acceptance criteria covered
+- [ ] Tests are deterministic (no live network, fixed seeds, injected clock)
+
+## Results
+- Command run: `<project unit-test command>`
+- Result: `<N passed / 0 failed>`
+
+## Whole-project coverage (re-run after implementation)
+> Required — coverage is re-run across the entire project once the code is green,
+> not just the changed files. The same numbers are recorded in `IMPLEMENT-SUMMARY.md`.
+- Coverage command: `<project coverage command>`
+- Total coverage: `<N>%` lines / `<N>%` branches
+- Meets target (≥ 80%): `<yes / no>`
+
+## Intentionally skipped
+- _(list any cases deferred to integration / execute-test, with the reason)_