Plans multi-step software tasks with file paths, tests, and commit messages.
npx skills add https://github.com/jlaws/dotfiles --skill writing-plans-jlaws
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/writing-plans Command: npx skills add https://github.com/jlaws/dotfiles --skill writing-plans-jlaws
Provides a structured, reproducible plan for implementing complex requirements by detailing which files to touch, exact steps, tests, and acceptance criteria before coding begins.
Create a new plan by naming the feature and writing bite-sized tasks with explicit file paths, tests, and commit steps.
High-intent search queries and answers about installing and using this skill.
Test-driven implementation steps break complex features into 2-5 minute tasks, each starting with a failing test and ending with a passing test. This ensures every code change is verifiable and guides incremental development with clear commit messages.
An implementation plan with exact file paths and tests details which files to modify, sample code, and acceptance criteria before coding begins. This artifact-driven approach provides a reproducible structure for multi-step software tasks.
Milestone grouping tracks progress on large system redesigns by organizing detailed task plans into optional milestones. This allows developers to monitor complex feature development phases and verify completion of major structural changes.
Test-driven planning works for spec-driven development and documentation tasks by detailing exact steps, tests, and acceptance criteria before coding begins. It produces a task-based plan that guides implementation with clear artifact references.
Commit messages and acceptance criteria for multi-step software tasks are structured within bite-sized task breakdowns. Each task specifies exact file paths, tests, and commit steps, ensuring reproducible implementation and clear milestones.
A detailed task-based plan for software engineering should not be used for simple modifications that do not require multi-step implementation or test alignment. It is designed for complex feature development where precise planning and documentation are required before coding.
poko8nadaGuide teams to gather requirements, define MVP scope, and break down tasks.
ernitptGenerate detailed implementation plans with file paths, code, tests, and commit messages.
srulytAssesses whether code meets acceptance criteria and passes tests.
projectedanxGenerate structured, test-driven implementation plans for software development tasks.
