technical-plan

Convert engineering specs into executable plan.md files with dependencies and risks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill technical-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-plan
Source: https://github.com/CleanExpo/Pi-Dev-Ops/tree/main/skills/technical-plan
Command: npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill technical-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes ambiguity from engineering work by converting a written specification into a concrete, file-by-file implementation plan with effort sizing, dependencies, risks, and a test stub.

Core Features & Use Cases

  • Spec-to-Plan Conversion: Reads a spec.md and outputs a ready-to-execute plan.md for the /build phase.
  • Implementation Precision: Produces an ordered set of atomic steps that map directly to files and functions to change or add.
  • Execution Guardrails: Includes pipeline identifiers, effort sizing, explicit dependency ordering, risk flags, and a structured test plan for unit, integration, manual, and regression coverage.
  • Pattern Alignment: Encourages referencing existing repo patterns (FastAPI modules, background tasks, skills injection, claude subprocess behavior, and state persistence conventions).

Quick Start

Use the technical-plan skill with your spec.md so it generates a plan.md that your /build phase can execute without additional clarification.

Frequently Asked Questions about technical-plan

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

FAQPage Schema
How do I convert an engineering spec into an executable implementation plan?

Spec-to-plan conversion works by reading a spec.md and generating a ready-to-execute plan.md that maps atomic steps directly to files and functions. This removes ambiguity by providing implementation precision for the build phase.

What should be included in a build plan to ensure safe execution by an autonomous agent?

A build plan for autonomous execution should include execution guardrails like pipeline identifiers, effort sizing, explicit dependency ordering, risk flags, and a structured test plan. These elements prevent errors during automated implementation.

Can I generate a FastAPI implementation plan that aligns with existing repository patterns?

Yes, spec-to-plan conversion encourages referencing existing repository patterns like FastAPI modules, background tasks, and state persistence conventions. This ensures the generated plan.md integrates smoothly with your current codebase structure.

What is the best way to size development effort and order work by dependencies?

The best way to size effort and order work by dependencies is to generate a plan.md that includes explicit effort sizing and pipeline dependency lists. This structures the build sequence to respect pipeline dependencies and map atomic steps to files.

Does the generated plan.md include a test plan for regression coverage?

Yes, the generated plan.md includes a structured test plan stub. This test plan covers unit, integration, manual, and regression testing to ensure comprehensive execution guardrails for the implementation steps.