Create structured implementation plans with file scope, tasks, tests, and success criteria.
npx skills add https://github.com/cruldra/skills --skill writing-plans-cruldra
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/cruldra/skills/tree/main/archived/writing-plans Command: npx skills add https://github.com/cruldra/skills --skill writing-plans-cruldra
Before coding, teams often lack a clear, executable plan, leading to scope creep, miscommunication, and rework.
请撰写一个完整的实施计划并保存为 docs/plans/YYYY-MM-DD-writing-plans.md。
High-intent search queries and answers about installing and using this skill.
A structured implementation plan for a complex software project is created by defining file scope, breaking down tasks, outlining testing plans, and setting clear success criteria before coding begins to ensure alignment and prevent scope creep.
Project planning to prevent scope creep and miscommunication should include defined boundaries, task breakdowns, file orchestration, testing plans, dependencies, and clear milestones to keep multi-team initiatives aligned before any code is written.
To plan multi-step tasks and milestones before touching code, generate a step-by-step executable plan that outlines task dependencies, deliverables, and file modifications, saving the comprehensive documentation for team reference.
Test-driven planning helps with task breakdown for multi-team initiatives by defining acceptance criteria and testing plans early, which guides implementation and keeps all teams aligned on clear deliverables and success criteria.
You can use this approach for any complex feature or multi-team initiative because it applies broadly to any scenario that benefits from a step-by-step executable plan, regardless of specific platforms or frameworks.
You should not use a comprehensive step-by-step plan for simple, single-step tasks where the overhead of defining file scope, milestones, and testing plans outweighs the benefits of preventing miscommunication and rework.
jrodrigopucaAnalyze repository structure to define documentation scope and complexity.
DFilipeSExecute implementation plans by writing code, running tests, and committing changes.
lazygophersExecute dependent tasks with up to two concurrent parallel runs.
lowmasonTransform vague specs into structured task plans with testable criteria.
