tech-plan

Convert PRD tasks into actionable TECH_PLAN.md files with milestone routing.

4|2|Updated Jan 29, 2026

Search Tags:#workflow #planning #architecture #documentation #PRD #milestones #tech-plan

Ready to run

npx skills add https://github.com/blake-simpson/belmont --skill tech-plan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Technical planning is the process of translating a PRD into a concrete, implementable TECH_PLAN, ensuring alignment across teams, milestones, and risk controls.

Core Features & Use Cases

Define master and per-feature TECH_PLAN.md structures and routing guidelines.
Map PRD tasks to concrete implementation actions and milestones, preserving cross-cutting decisions.
Enforce alignment between PRD, PROGRESS, and TECH_PLAN to minimize drift.

Quick Start

Run the Belmont tech-plan flow to generate or update the master and feature TECH_PLAN.md documents with aligned implementation details.

Frequently Asked Questions about tech-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert a PRD into an actionable technical plan?▼

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.

How do I map PRD tasks to specific implementation milestones?▼

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.

What's the best way to document cross-cutting architecture decisions during planning?▼

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.

Does this technical planning workflow support per-feature documentation?▼

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.

Why does my technical plan drift from the original PRD requirements?▼

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.