Generate structured implementation plans with acceptance criteria saved to ./plans/.
npx skills add https://github.com/hschne/pi-stuff --skill plan-hschne
Please help me install this Agent Skill. Skill: plan Source: https://github.com/hschne/pi-stuff/tree/main/skills/plan Command: npx skills add https://github.com/hschne/pi-stuff --skill plan-hschne
This skill eliminates the frustration of creating vague, unstructured implementation plans that lack clear steps, acceptance criteria, and scope, ensuring your project roadmaps are actionable and aligned with team requirements.
Ask the AI to create a step-by-step implementation plan for adding password reset functionality to your web app, and it will generate a validated, scoped plan saved to your ./plans/ directory.
High-intent search queries and answers about installing and using this skill.
To create an actionable implementation plan, use a guided workflow that runs a requirement-gathering interview to clarify constraints, then generates a structured roadmap with numbered steps, explicit file changes, and acceptance criteria.
Scoping work breakdown for code refactoring requires defining out-of-scope work and priorities first. A validated plan template enforces this structure by mandating clear non-goals and acceptance criteria before generating step-by-step tasks.
Generating a step-by-step project roadmap with acceptance criteria involves applying a standardized template that validates each task has explicit file changes and verifiable outcomes, ensuring the plan is actionable rather than a vague draft.
Implementation plan validation requires specifying file changes and non-goals. A mandatory validation checklist enforces that every scoped task includes explicit file modifications, acceptance criteria, and clear boundaries for deferred features.
You can use a guided scoping workflow for feature development planning. It automatically prompts you for tech stack details, deadlines, and deferred features before drafting any plan, ensuring the output aligns with team requirements.
Generated software development plans are saved directly to your project's local ./plans/ directory. This ensures your validated, scoped roadmaps are immediately accessible within your existing codebase structure.
jeremy-newhousePlan and register an end-to-end project kickoff with tech stack, architecture, documentation, and feature backlog.
JingyiWngGenerate implementation-ready tech specs from natural language requirements.
Jeff-StapletonAutomate story implementation, build verification, and version control operations.
forketyforkConvert vague project tasks into structured Markdown implementation plans.
