Generate step-by-step implementation plans from a given spec.
npx skills add https://github.com/revokslab/ShipFree --skill writing-plans-revokslab
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/revokslab/ShipFree/tree/main/.cursor/skills/writing-plans Command: npx skills add https://github.com/revokslab/ShipFree --skill writing-plans-revokslab
This Skill helps engineers transform a product spec or requirements into a detailed, executable plan before coding.
Describe the feature to implement and its acceptance criteria, then run the Skill to generate a plan. The tool saves the output to docs/plans/YYYY-MM-DD-<feature-name>.md
High-intent search queries and answers about installing and using this skill.
To generate an implementation plan from a spec, describe your feature and acceptance criteria, and the tool outputs a step-by-step plan with file touchpoints, testing steps, and commits saved to docs/plans/YYYY-MM-DD-<feature-name>.md.
Task breakdown for engineering documentation divides feature development or refactoring into bite-sized executable steps. It outlines files to touch, code samples, tests, and commits while adhering to DRY, YAGNI, and TDD principles.
Yes, you can use this for refactoring and documentation tasks across codebases. It transforms requirements into comprehensive plans covering design, implementation, testing, and deployment steps for engineers.
The best way to turn requirements into executable code steps is using a planning tool that applies DRY, YAGNI, and TTD principles. It provides task granularity, suggested testing strategies, and references to relevant files.
Yes, the generated plan includes testing strategies and file references. It provides guidance and references to relevant files and standards, alongside detailed code samples and commit milestones.
Generated implementation plans are saved as markdown files in the docs/plans/ directory. The output file is automatically named using the YYYY-MM-DD-<feature-name>.md format for chronological tracking.
lluppesmsGenerate structured Markdown PRDs from Epic feature descriptions.
tridigitalsGenerate task-oriented implementation plans with files, tests, docs, and commits from specs.
lagz0neGenerate end-to-end implementation plans from product specs with frontmatter metadata.
BaraArdiwinataDecompose feature specifications into implementable tasks with dependency tracking and acceptance criteria.
