feat

Enrich feature descriptions and generate a two-stage PM and Architect plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature development often suffers from fragmented requirements and inconsistent planning. This skill provides a disciplined two-stage workflow (PM enrichment followed by Architect planning) to generate a single, cohesive feature document that aligns business and technical perspectives.

Core Features & Use Cases

  • PM enrichment: adds problem statements, business value, objectives, scope, and success criteria.
  • Architect planning: derives technical development phases, dependencies, and deliverables.
  • Output: a versioned feature directory feat-YYYY-MM-{slug} with a combined feature document and cross-references.

Quick Start

Provide a feature description to /feat and let the PM enrich it before the Architect develops the technical plan.

Frequently Asked Questions about feat

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

FAQPage Schema
How do I create a feature document with both PM requirements and technical architecture?

Feature planning aligns business and technical perspectives by running a two-stage PM and Architect workflow. It enriches descriptions with problem statements and objectives, then derives technical phases and deliverables into a single cohesive document.

What is the best way to structure feature planning for fragmented requirements?

A disciplined two-stage workflow structures feature planning by first adding problem statements and success criteria, then deriving technical dependencies. It outputs a versioned feature directory with cross-referenced documentation to resolve fragmented requirements.

How do I generate a versioned feature directory with success criteria and development phases?

You generate a versioned feat-YYYY-MM-{slug} directory by providing a feature description to the planning workflow. It automatically creates a combined document referencing related documentation, success criteria, development phases, and proposed high-level subtasks.

Does the feature planning workflow propose high-level subtasks automatically?

Yes, the feature planning workflow automatically proposes high-level subtasks when relevant. During the Architect planning stage, it derives these subtasks alongside technical development phases, dependencies, and deliverables for the feature document.

Can I use this two-stage PM and Architect workflow without external dependencies?

Yes, you can use this two-stage PM and Architect workflow without external dependencies. It operates independently to enrich feature descriptions with objectives and scope, then generates a combined feature document validating the technical plan.