Transform approved feature specifications into ordered atomic technical build plans.
npx skills add https://github.com/bernajaber/pi-product-system --skill plan-bernajaber
Please help me install this Agent Skill. Skill: plan Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/plan Command: npx skills add https://github.com/bernajaber/pi-product-system --skill plan-bernajaber
This Skill transforms an approved feature specification into a precise, ordered technical build plan so autonomous agents can implement features reliably without operator interaction.
Create a technical plan for the feature defined in .pi/specs/<feature>/spec.md and save it to .pi/specs/<feature>/plan.md.
High-intent search queries and answers about installing and using this skill.
To turn a feature spec into an atomic build plan, you apply this Skill to your spec.md file. It generates an ordered plan.md with atomic tasks where each task is independently testable, mapped to acceptance scenarios, and corresponds to a single commit.
An atomic task in a technical build plan is a single, independently testable unit of work that corresponds to one commit. It includes a clear "Done when" condition and maps directly to an acceptance scenario from the feature specification.
You can generate a file structure and select a stack by processing your approved feature spec. This Skill selects a minimal, mature stack by justifying choices against engineering constitutions and defines the project file structure within the output plan.
Yes, you need an approved specification. The Skill requires a spec.md input located in .pi/specs/<feature>/ and checks that workflow-state.json currentPhase is set to analyze before generating the technical plan.
The best way to structure tasks for autonomous agents is creating an ordered list of atomic tasks. This Skill produces a plan.md where each task is independently testable, mapped to acceptance scenarios, and ends with a final "Write Tests" task.
When creating a technical build plan, the Skill updates REVIEW_GUIDELINES.md and workflow-state.json. It also creates a feature branch and saves the generated plan to .pi/specs/<feature>/plan.md for downstream build and test skills.
bernajaberConvert approved briefs into testable acceptance scenarios in spec.md files.
bernajaberRun and validate automated acceptance tests for product features.
EmrebenerCoordinate spec-driven development workflows with enforced stage ordering and approval gates.
ogprotegeReview recently written code for architectural consistency and system integration.
