Generate implementation plans with file paths, tests, and commands.
npx skills add https://github.com/maraxen/praxis --skill writing-plans-maraxen
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/maraxen/praxis/tree/main/.agent/skills/writing-plans Command: npx skills add https://github.com/maraxen/praxis --skill writing-plans-maraxen
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Create a new implementation plan for a feature and save it under docs/plans/YYYY-MM-DD-<feature-name>.md
High-intent search queries and answers about installing and using this skill.
To turn feature specs into actionable implementation plans, generate a standardized structure with bite-sized tasks, explicit file paths, testing steps, and example commands, ensuring zero-context guidance for developers.
The best way to break a feature into tasks, tests, and milestones is enforcing a standardized plan structure that documents every action, file touchpoint, and validation step required to reproduce the work.
Test-driven development fits into task breakdown documentation by enforcing TDD practices alongside DRY and YAGNI principles, ensuring each bite-sized task includes explicit testing steps and frequent commits.
Yes, you can save implementation plans to a conventional location like docs/plans/YYYY-MM-DD-<feature-name>.md and reuse worktrees to support iterative brainstorming across multi-step tasks.
Yes, you need to specify file touchpoints when generating multi-step task plans so engineers with zero codebase context know exactly which files to touch, check, and test for each milestone.
You should use standardized plan structures for feature implementation to provide zero-context guidance, preventing assumptions about codebase familiarity and ensuring all actions, tests, and documentation are explicitly defined.
lllyysGenerate implementation plans with rules, dependencies, and work items.
boazcstrikeGenerate step-by-step implementation plans with file modifications, code snippets, testing commands, and commit instructions.
droxeyTranslate software specs into file-aware implementation plans with test strategy.
mchien15Visualize plan progress and milestones on a local HTTP dashboard.
