skills.rest
tmchow
tmchowCOMMUNITY
Explore all skills by this author →
Website𝕏@trevinGitHub

iterative:tech-planning

Create an executable technical plan from a PRD or requirements.

22|2|Updated Jan 23, 2026
Search Tags:#planning#architecture#documentation#requirements#prd#technical-plan#test-scenarios
One-click install
npx skills add https://github.com/tmchow/tmc-marketplace --skill iterative-tech-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iterative:tech-planning
Source: https://github.com/tmchow/tmc-marketplace/tree/main/plugins/iterative-engineering/skills/tech-planning
Command: npx skills add https://github.com/tmchow/tmc-marketplace --skill iterative-tech-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turn a PRD or set of requirements into a structured, executable implementation plan. Write as if the implementer has zero context for the codebase — document the decisions, the reasoning, and enough detail that they can start working without asking clarifying questions.

Core Features & Use Cases

  • Transforms a PRD or set of requirements into a concrete, executable plan that specifies WHAT to build and WHERE to implement it.
  • Captures architecture decisions, trade-offs, dependencies, and test scenarios to guide development.
  • Can be invoked after brainstorming or standalone with existing requirements to produce a ready-to-implement plan.

Quick Start

Provide a PRD or requirements and let this skill generate a concrete technical plan that an implementer can start coding from.

Frequently Asked Questions about iterative:tech-planning

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

FAQPage Schema
How do I turn a PRD into an actionable technical plan?▼

A technical plan captures architectural decisions, trade-offs, and rationale from a PRD to guide development. It specifies exactly what files to create or modify and defines concrete test scenarios for the implementer.

What should a technical implementation plan include for developers?▼

A technical implementation plan should enumerate files to create or modify, capture architectural decisions and rationale, specify concrete test scenarios and related files, and align with the PRD requirements.

Can I generate implementation plans from requirements without a full PRD?▼

Yes, you can generate implementation plans from existing requirements without a full PRD. The skill applies standalone with existing requirements or after brainstorming to produce a structured, executable technical plan.

How do I document architecture decisions and trade-offs in a development plan?▼

Document architecture decisions and trade-offs by capturing the reasoning and dependencies alongside the specified files. The skill writes detailed rationale so an implementer can start coding without asking clarifying questions.

When do I need to create a technical plan from requirements?▼

You need to create a technical plan when requirements are clear and an implementation plan is needed. It applies after brainstorming or standalone to bridge the gap between a PRD and executable code by detailing what to build and where.

Related Skills

Explore More Software Engineering Skills→
simoneschiavosimoneschiavo

prd-generator

Generate a structured PRD with acceptance criteria from a feature description.

Community
Intermediate
krzemienskikrzemienski
2

writing-plans

Generate implementation plans with tasks, file paths, tests, and quantitative metrics.

Community
Advanced
congthang12312congthang12312

brainstorm

Generate structured architecture options with trade-offs and guardrails for design decisions.

Community
Advanced
GabeujinGabeujin

breakdown-test

Generate test strategies, task breakdowns, and QA plans for GitHub projects.

Community
Advanced