Generate a dependency-ordered implementation plan from a validated specification.
npx skills add https://github.com/Pyl-Tech/stream-coding --skill plan-pyl-tech
Please help me install this Agent Skill. Skill: plan Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/plan Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill plan-pyl-tech
It prevents AI from jumping into implementation too early by converting a validated spec into a structured, verifiable implementation plan that is ready for explicit confirmation.
Use the plan skill to produce an end-to-end implementation plan from the validated spec and wait for explicit confirmation before any code is written.
High-intent search queries and answers about installing and using this skill.
Generating an implementation plan from a validated spec requires converting spec items into dependency-ordered, vertically sliced steps with mapped test strategies. This prevents premature implementation by ensuring every endpoint, model, and UI item is explicitly enumerated and checked against a final exit gate.
Vertical slicing in implementation planning is the breakdown of work into small, dependency-ordered steps that deliver complete functional units. Each slice includes mapped acceptance criteria, identified risks with mitigations, and test strategies to ensure verifiable progress.
Creating cross-module interface contracts involves generating a shared artifact that defines request and response shapes, shared types, and error formats for interacting modules. This avoids exposing internal details and ensures modules interact safely during multi-step implementation.
Yes, you need a fully validated spec before planning multi-step software implementations. Planning requires passing a Spec Gate with a perfect score and an Adversarial Review with no critical issues to prevent jumping into code generation prematurely.
Limitations of AI spec validation and implementation planning include the refusal to generate a plan if the Spec Gate score is imperfect or if Adversarial Review finds critical issues. It also requires explicit deferrals for omitted spec items to ensure nothing is silently missed.
MysMonValidate specification and design documents against explicit criteria before stakeholder review.
oxieBreak down implementation plans into 20-30 testable tasks with acceptance criteria.
mia-cxGenerate multiple radically different interface designs for a module.
unipds-engenharia-de-ia-aplicadaGenerate dependency-ordered implementation tasks from feature design artifacts.
