Generate step-by-step implementation plans from formal specs.
npx skills add https://github.com/SlevoDev/s-tag --skill writing-plans-slevodev
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/SlevoDev/s-tag/tree/main/.claude/skills/writing-plans Command: npx skills add https://github.com/SlevoDev/s-tag --skill writing-plans-slevodev
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.
Generate a complete, task-by-task implementation plan from a formal feature spec.
High-intent search queries and answers about installing and using this skill.
To turn a feature spec into an implementation plan, you generate step-by-step task breakdowns detailing exact file changes, testing strategies, and commit messages. This ensures engineers without prior codebase context can execute the feature development effectively.
Test-driven development planning for codebase onboarding is generating detailed task breakdowns specifying exact file changes, tests, and integration steps. It guides engineers with zero codebase context through feature implementation using bite-sized, executable tasks.
To break down a development spec into tasks for engineers, generate a complete executable plan outlining specific file touchpoints, tests, docs, and review criteria. Applying DRY and YAGNI principles keeps tasks bite-sized and manageable for implementation.
Implementation planning works for cross-functional software tasks by outlining exact file changes, testing strategies, and integration steps. It applies to feature development and onboarding, ensuring engineers have clear validation criteria and commit messages.
An implementation plan for TDD and frequent commits should specify exact file changes, testing strategies, validation criteria, and commit messages. It must provide engineers with bite-sized tasks detailing code, tests, and docs to check.
cookeyholderDefine a formal spec before coding to guide planning and implementation.
corticalstackInspect git status and diffs, stage specific files, and commit with imperative messages.
rhussGenerate implementation plans and TDD cycles from validated specifications.
royhenengelGenerate spec-driven implementation plans for software development tasks.
