Generate bite-sized TDD implementation plans from a spec into plan.md.
npx skills add https://github.com/Mrlyk/superharness --skill writing-plans-mrlyk
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/Mrlyk/superharness/tree/main/skills/writing-plans Command: npx skills add https://github.com/Mrlyk/superharness --skill writing-plans-mrlyk
The Writing Plans skill helps engineers convert a spec or requirements into concrete, bite-sized implementation tasks, ensuring every necessary step is documented before coding begins.
Summarize the spec into bite-sized, TDD-ready tasks and save the plan to .superharness/tasks/{MM}-{DD}-{name}/plan.md.
High-intent search queries and answers about installing and using this skill.
Decomposing a software spec into TDD-ready steps involves generating bite-sized tasks mapping to specific files and tests. This skill creates a plan.md with 2-5 minute steps, explicit commit points, and testing guidance saved to .superharness/tasks/.
The best way to create task decomposition for high-ambiguity specs is converting requirements into concrete, documented tasks before coding. This approach enforces a TDD-driven workflow with clear modification guidance, testing steps, and commit-ready milestones.
Generating an implementation plan with explicit commit points requires breaking specs into 2-5 minute actionable steps. The output plan.md documents specific file modifications, maps testing procedures, and defines commit-ready milestones for repeatable TDD workflows.
Yes, you can use this task planning workflow for projects with unclear requirements. It enables rapid, repeatable planning by summarizing ambiguous specs into bite-sized, TDD-ready tasks with comprehensive documentation mapping.
No, this planning approach requires no external dependencies or components. It operates standalone to produce a plan.md file saved directly to the .superharness/tasks/{MM}-{DD}-{name}/ directory structure.
Your TDD workflow needs bite-sized task decomposition to ensure every necessary step is documented before coding begins. It maps tasks to specific files, tests, and documentation, reducing ambiguity and enforcing a repeatable 2-5 minute step workflow.
hamzaPixlParse PRD files, URLs, or text into structured requirements artifacts.
ryan-mahoneyExecute GitHub issue steps sequentially with targeted tests and conventional commits.
clowaExecute unit tests against Terraform modules without provisioning real infrastructure.
nnexaiCapture, list, and promote unstructured notes into structured todo items.
