Generate executable implementation plans with TDD tasks and exact file paths.
npx skills add https://github.com/Z43L/zeus-agent --skill writing-plans-z43l
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/Z43L/zeus-agent/tree/main/skills/software-development/writing-plans Command: npx skills add https://github.com/Z43L/zeus-agent --skill writing-plans-z43l
It solves the problem of turning ambiguous requirements into a concrete, testable implementation plan that covers files, commands, and verification steps.
Use writing-plans to produce an implementation plan for your feature by asking Zeus to generate tasks with exact file paths, full TDD cycles, and a saved docs/plans entry.
High-intent search queries and answers about installing and using this skill.
Implementation plans are generated by breaking software requirements into bite-sized, testable tasks that specify exact file paths, test locations, and verification commands. This approach produces an execution-ready structure covering complete TDD cycles and commit instructions.
A TDD-aligned task breakdown splits feature development into 2–5 minute steps where each code task includes a failing test, expected failure, minimal implementation, expected pass, and verification commands to reduce cognitive load and prevent stalling.
Creating an implementation plan for subagent-driven development involves generating explicit handoff structures with exact file paths, full TDD cycles, and frequent commit instructions so an implementer with limited context can follow a clear execution path.
Yes, this implementation planning approach applies to multi-step feature development and refactors by producing execution-ready plans that specify exact file paths, test locations, and verification commands for the implementer.
Yes, the generated implementation plan satisfies requirements for TDD-aligned task sequencing, DRY/YAGNI guidance, frequent commits, and an explicit handoff structure to ensure minimal guesswork during code execution.
Planning code tasks in 2-5 minute steps reduces cognitive load and prevents stalling, but it requires complete specification of exact file paths, test locations, and verification commands to ensure the implementer can proceed without guessing.
PickleSodaDesign step-by-step implementation plans for multi-step software tasks.
woodrowpearsonGenerate implementation plans with file paths, code samples, tests, and verification steps.
shynlee04Enforces the RED phase of TDD by requiring a failing test before implementation code.
zhizhunbaoGenerate sprint backlogs, user stories, and task breakdowns from PRD requirements.
