plan

Generate Markdown feature implementation plans with steps, risks, and acceptance criteria.

4|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/matochu/pythia --skill plan-matochu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/matochu/pythia/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/matochu/pythia --skill plan-matochu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to generate hermetic, feature-specific implementation plans that describe concrete steps, risks, acceptance criteria, and necessary cross-links, ensuring consistent planning across architectures.

Core Features & Use Cases

  • Plan generation: Produces a complete Markdown plan with Plan-Id, Plan-Version, Last review round, Plan revision log, and a navigable structure.
  • Ambiguity handling: Enforces architecture ambiguity checkpoints and captures user decisions before proceeding.
  • Cross-linking & Validation: Updates relevant contexts with references to the new plan and prepares validator-friendly validation instructions.

Quick Start

Provide a feature context and plan slug to generate a complete plan document you can save.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a feature implementation plan in Markdown that includes risks and acceptance criteria?▼

To generate a feature implementation plan in Markdown, provide feature context and a plan slug to produce a complete document with concrete steps, risks, acceptance criteria, and cross-references.

What is a hermetic feature plan and when do I need one for software architecture?▼

A hermetic feature plan is a feature-specific implementation document that isolates development steps and metadata. You need one to ensure consistent planning and execution across complex software architectures.

How do I add plan metadata like Plan-Id, Plan-Version, and revision logs to my workflow?▼

You can add plan metadata like Plan-Id, Plan-Version, and revision logs by generating a navigable Markdown document that automatically includes these fields along with last review round tracking.

Can I enforce architecture ambiguity checkpoints before proceeding with feature plan generation?▼

Yes, the feature plan generation workflow enforces architecture ambiguity checkpoints to capture user decisions and resolve uncertainties before proceeding with the final plan creation.

Does the feature plan workflow update cross-references and prepare validation hooks automatically?▼

Yes, the workflow updates relevant architectural contexts with references to the new plan and prepares validator-friendly validation instructions to ensure feature implementation integrity.