Scribe MCP Server

# ⚙️ Phase Plan — {{PROJECT_NAME}} **Author:** {{AUTHOR}} **Version:** Draft v0.1 **Last Updated:** {{DATE_UTC}} > TODO: Derive this plan from the Architecture Guide. Each phase should deliver a reviewable increment and reference the checklist items it will produce. --- ## Phase Overview <!-- ID: phase_overview --> | Phase | Goal | Key Deliverables | Confidence (0-1) | |-------|------|------------------|------------------| | Phase 0 | {{FILL_ME}} | {{FILL_ME}} | 0.70 | | Phase 1 | {{FILL_ME}} | {{FILL_ME}} | 0.65 | | Phase 2 | {{FILL_ME}} | {{FILL_ME}} | 0.55 | Update this table as the project evolves. Confidence values should change as knowledge increases. --- ## Phase 0 — {{PHASE0_NAME}} <!-- ID: phase_0 --> **Objective:** {{FILL_ME}} **Key Tasks:** - [ ] {{TASK_0_1}} - [ ] {{TASK_0_2}} - [ ] {{TASK_0_3}} **Deliverables:** - {{DELIVERABLE_0_1}} - {{DELIVERABLE_0_2}} **Acceptance Criteria:** - [ ] {{CRITERIA_0_1}} - [ ] {{CRITERIA_0_2}} **Dependencies:** {{DEPENDENCIES_0}} **Notes:** Capture risks, blockers, or decisions specific to this phase. --- ## Phase 1 — {{PHASE1_NAME}} <!-- ID: phase_1 --> Repeat the pattern above for each additional phase. Ensure tasks are actionable and tie back to Architecture + Checklist entries. --- ## Milestone Tracking <!-- ID: milestone_tracking --> | Milestone | Target Date | Owner | Status | Evidence/Link | |-----------|-------------|-------|--------|---------------| | {{MILESTONE_1}} | {{DATE}} | {{OWNER}} | {{STATUS}} | {{LINK}} | Update status and evidence as work progresses. Always link to PROGRESS_LOG entries or commits. --- ## Retro Notes & Adjustments <!-- ID: retro_notes --> - Summarise lessons learned after each phase completes. - Document any scope changes or re-planning here.