Convert PRD tasks into actionable TECH_PLAN.md files with milestone routing.
npx skills add https://github.com/blake-simpson/belmont --skill tech-plan
Please help me install this Agent Skill. Skill: tech-plan Source: https://github.com/blake-simpson/belmont/tree/main/plugin/skills/tech-plan Command: npx skills add https://github.com/blake-simpson/belmont --skill tech-plan
Technical planning is the process of translating a PRD into a concrete, implementable TECH_PLAN, ensuring alignment across teams, milestones, and risk controls.
Run the Belmont tech-plan flow to generate or update the master and feature TECH_PLAN.md documents with aligned implementation details.
High-intent search queries and answers about installing and using this skill.
A technical plan translates PRD requirements into actionable implementation details by defining file structures, component patterns, and architecture decisions, outputting structured TECH_PLAN.md documents for team alignment.
You map PRD tasks to implementation milestones by enforcing consistency and milestone routing rules within the TECH_PLAN, preserving cross-cutting architecture decisions and minimizing drift between documents.
The best way to document cross-cutting architecture decisions during planning is by generating master and feature TECH_PLAN.md files that enforce alignment between PRD, PROGRESS, and implementation actions.
Yes, this technical planning workflow supports per-feature documentation by generating individual feature TECH_PLAN.md files alongside a master plan, applying cross-cutting architecture decisions and routing guidelines to each feature.
Your technical plan drifts from PRD requirements when alignment is not enforced between the PRD, PROGRESS, and TECH_PLAN documents, which this planning process mitigates by mapping tasks to concrete implementation actions.
vfarcicGenerate GitHub issues and PRD files with milestone-based planning.
zm2231Track goals across timeframes with milestones, metrics, and progress reports.
devalexanderdazaGenerate sprint-status.yaml files from epic markdown documents.
lossyrobCompare implementation diffs against project specifications to identify gaps.
