@drafthq/draft 3.5.3 → 3.7.1

package/core/templates/service-index.md

@@ -43,6 +43,7 @@ The following services have not been initialized with `/draft:init`:
 - `[path/to/service]/`
 
 Initialize each one by running `/draft:init` inside its directory — it links the module's graph up to the root spine:
+
 ```bash
 cd [path/to/service] && /draft:init
 ```

package/core/templates/spec.md

@@ -45,6 +45,7 @@ approvers:
 > is rendered from `metadata.json:status`; never edit it inline.
 
 ## Context References
+
 - **Product:** `draft/product.md` — [pending]
 - **Tech Stack:** `draft/tech-stack.md` — [pending]
 - **Architecture:** `draft/.ai-context.md` — [pending]
@@ -59,16 +60,21 @@ approvers:
 > `<!-- VERIFIER:IGNORE END -->` so they don't fail the verifier.
 
 ## Problem Statement
+
 [To be developed through intake conversation]
 
 ## Background & Why Now
+
 [To be developed through intake conversation]
 
 ## Requirements
+
 ### Functional
+
 [To be developed through intake conversation]
 
 ### Non-Functional
+
 [To be developed through intake conversation]
 
 ## Acceptance Criteria
@@ -82,9 +88,11 @@ approvers:
 | AC-2 | _TBD_ac_2_description_ | _TBD_ac_2_test_id_ |
 
 ## Non-Goals
+
 [To be developed through intake conversation]
 
 ## Technical Approach
+
 [To be developed through intake conversation]
 
 ## Eligibility / Cap Policy <!-- OPTIONAL -->
@@ -118,6 +126,7 @@ approvers:
 | QA | _TBD_approver_qa_ | Test plan review | [ ] |
 
 ### Approval Gates
+
 - [ ] Spec approved by Product Owner
 - [ ] Architecture reviewed by Tech Lead
 - [ ] Security review completed (if touching auth, data, or external APIs)
@@ -138,29 +147,35 @@ approvers:
 <!-- Define rollout approach for production delivery -->
 
 ### Rollout Phases
+
 1. **Canary** (1-5% traffic) — Validate core flows, monitor error rates
 2. **Limited GA** (25%) — Expand to subset, watch performance metrics
 3. **Full GA** (100%) — Complete rollout
 
 ### Feature Flags
+
 - Flag name: `[feature_flag_name]`
 - Default: `off`
 - Kill switch: [yes/no]
 
 ### Rollback Plan
+
 - Trigger: [e.g., error rate >1%, latency >500ms p95]
 - Process: [e.g., disable feature flag, revert deployment]
 - Data rollback: [e.g., migration revert script, N/A]
 
 ### Monitoring
+
 - Dashboard: [link or name]
 - Alerts: [e.g., PagerDuty rule for error rate spike]
 - Key metrics: [e.g., error rate, latency, throughput]
 
 ## Open Questions
+
 [Tracked during conversation]
 
 ## Conversation Log
+>
 > Key decisions and reasoning captured during intake.
 
 [Conversation summary will be added here]

package/core/templates/tech-stack.md

@@ -29,12 +29,14 @@ generated_at: "{ISO_TIMESTAMP}"
 ## Frameworks & Libraries
 
 ### Core
+
 | Name | Version | Purpose |
 |------|---------|---------|
 | [Framework] | [Version] | [Purpose] |
 | [Library] | [Version] | [Purpose] |
 
 ### Development
+
 | Name | Version | Purpose |
 |------|---------|---------|
 | [Tool] | [Version] | [Purpose] |
@@ -64,14 +66,17 @@ generated_at: "{ISO_TIMESTAMP}"
 ## Build & Deploy
 
 ### Build
+
 - **Tool**: [Webpack/Vite/esbuild/etc]
 - **Output**: [dist/build/etc]
 
 ### CI/CD
+
 - **Platform**: [GitHub Actions/CircleCI/etc]
 - **Triggers**: [on push, PR, etc]
 
 ### Deployment
+
 - **Target**: [Vercel/AWS/GCP/etc]
 - **Environments**: [dev, staging, prod]
 
@@ -80,18 +85,22 @@ generated_at: "{ISO_TIMESTAMP}"
 ## Code Patterns
 
 ### Architecture
+
 - **Pattern**: [Clean Architecture/MVC/Hexagonal/etc]
 - **Rationale**: [Why this pattern]
 
 ### State Management
+
 - **Approach**: [Redux/Zustand/Context/etc]
 - **Rationale**: [Why this approach]
 
 ### Error Handling
+
 - **Strategy**: [Centralized/per-module/etc]
 - **Logging**: [Tool/service]
 
 ### API Design
+
 - **Style**: [REST/GraphQL/gRPC]
 - **Conventions**: [Naming, versioning]
 
@@ -140,15 +149,18 @@ graph TD
 ## Code Style
 
 ### Linting
+
 - **Tool**: [ESLint/Prettier/etc]
 - **Config**: [.eslintrc / prettier.config.js]
 
 ### Formatting
+
 - **Indentation**: [2 spaces / 4 spaces / tabs]
 - **Line Length**: [80 / 100 / 120]
 - **Quotes**: [single / double]
 
 ### Naming Conventions
+
 - **Files**: [kebab-case / camelCase / PascalCase]
 - **Functions**: [camelCase]
 - **Classes**: [PascalCase]

package/core/templates/workflow.md

@@ -31,6 +31,7 @@ synced_to_commit: "{FULL_SHA}"
 **Mode:** [strict | flexible | none]
 
 **Coverage Target:**
+
 ```yaml
 coverage_target: 95  # Minimum coverage percentage (default: 95%)
 ```
@@ -40,11 +41,13 @@ coverage_target: 95  # Minimum coverage percentage (default: 95%)
 **Iron Law:** No production code without a failing test first.
 
 The Cycle:
+
 1. **RED** - Write failing test, run it, VERIFY it FAILS
 2. **GREEN** - Write minimum code, run test, VERIFY it PASSES
 3. **REFACTOR** - Clean up, keep tests green throughout
 
 **Red Flags - Delete and Restart if:**
+
 - Code written before test exists
 - Test passes immediately (testing wrong thing or wrong code)
 - "Just this once" rationalization
@@ -52,17 +55,20 @@ The Cycle:
 - Running test mentally instead of actually
 
 **Checklist:**
+
 - [ ] Test written and committed BEFORE implementation
 - [ ] Test fails with expected failure (not syntax error)
 - [ ] Minimum code to pass (no extra features)
 - [ ] Refactor preserves green state
 
 ### Flexible TDD
+
 - [ ] Tests required but can be written after implementation
 - [ ] All code must have tests before marking complete
 - [ ] Refactoring encouraged
 
 ### No TDD
+
 - [ ] Tests optional
 - [ ] Manual verification acceptable
 
@@ -73,6 +79,7 @@ The Cycle:
 **Format:** `type(scope): description`
 
 ### Types
+
 | Type | Use For |
 |------|---------|
 | `feat` | New feature |
@@ -84,10 +91,12 @@ The Cycle:
 | `chore` | Build, tooling, dependencies |
 
 ### Scope
+
 - Use track ID for Draft work: `feat(add-auth): ...`
 - Use component name otherwise: `fix(api): ...`
 
 ### Commit Frequency
+
 - [ ] After each task completion
 - [ ] At phase boundaries
 - [ ] End of session
@@ -97,6 +106,7 @@ The Cycle:
 ## Code Review
 
 ### Self-Review Checklist
+
 - [ ] Code follows project style guide
 - [ ] Tests pass locally
 - [ ] No console.log or debug statements
@@ -104,6 +114,7 @@ The Cycle:
 - [ ] Edge cases considered
 
 ### Before Marking Task Complete
+
 - [ ] Run linter
 - [ ] Run tests
 - [ ] Review diff
@@ -126,11 +137,13 @@ Do not proceed to next phase until verification passes.
 ## Review Settings
 
 ### Auto-Review
+
 - [ ] Auto-review at track completion
 
 When enabled, runs `/draft:review track <id>` automatically when `/draft:implement` completes a track.
 
 ### Blocking Behavior
+
 - [ ] Block on review failures
 
 When enabled, halt track completion if critical (✗) issues found. Requires fixes before marking complete.
@@ -138,6 +151,7 @@ When enabled, halt track completion if critical (✗) issues found. Requires fix
 When disabled (default), review failures produce warnings only. Issues documented in `draft/tracks/<id>/review-report.md`.
 
 ### Review Scope (Stage 1 Automation)
+
 - [x] Architecture conformance
 - [x] Dead code detection
 - [x] Dependency cycle detection
@@ -153,17 +167,21 @@ Uncheck categories to skip during validation phase of review. All enabled by def
 ## Session Management
 
 ### Starting a Session
+
 1. Run `/draft:status` to see current state
 2. Read active track's spec.md and plan.md
 3. Find current task (marked `[~]` or first `[ ]`)
 
 ### Ending a Session
+
 1. Commit any pending changes
 2. Update plan.md with progress
 3. Add notes for next session if mid-task
 
 ### Context Handoff
+
 If task exceeds 5 iterations:
+
 1. Document current state in plan.md
 2. Note any discoveries or blockers
 3. Suggest resumption approach
@@ -173,9 +191,11 @@ If task exceeds 5 iterations:
 ## Toolchain
 
 ### VCS
+
 - [x] git + GitHub Pull Requests
 
 ### MCP Auto-Connect (optional)
+
 - [ ] Jira MCP — for ticket linking via `/draft:jira` (preview / create / review)
 - [ ] Confluence MCP — for design-doc and runbook lookups