Generate implementation plans with TDD steps, commands, and saved file paths.
npx skills add https://github.com/thiansit/LuPang --skill writing-plans-thiansit
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/thiansit/LuPang/tree/main/.claude/skills/writing-plans Command: npx skills add https://github.com/thiansit/LuPang --skill writing-plans-thiansit
The writing-plans skill transforms vague specs or requirements into concrete, test-driven, bite-sized engineering tasks so developers can implement features with minimal ramp-up time and without prior knowledge of the codebase.
Create an implementation plan for adding feature X that includes failing tests, exact file changes, test commands, expected results, and commit messages and save it to docs/plans/YYYY-MM-DD-feature-x.md.
High-intent search queries and answers about installing and using this skill.
To turn a software specification into a test-driven implementation plan, you provide the feature requirements to generate a structured document. The output includes architecture summaries, file-specific actions, failing-test examples, and exact run commands for step-by-step execution.
The best way to break down engineering tasks for developers lacking project context is generating bite-sized, 2-5 minute actionable steps. Each step contains explicit file paths, minimal implementation snippets, expected test outcomes, and commit instructions to minimize ramp-up time.
You generate TDD-style task breakdowns by processing specifications into tasks that pair failing-test examples with minimal implementation snippets. The plan details exact run commands alongside their expected outputs and provides commit guidance for each incremental step.
Yes, you can hand off implementation plan execution to subagents or parallel sessions. The generated plan file includes explicit execution modes designed to distribute follow-up work directly to automated agents or separate developer worktrees without further manual task breakdown.
Generated implementation plan files should be saved under the docs/plans/ directory using a YYYY-MM-DD-<feature-name>.md naming convention. This standardized storage path ensures new developers can easily locate and execute structured onboarding tasks.
Writing-plans works for software refactors, tests, and documentation, not just new features. It applies to any multi-step engineering task requiring step-by-step preparation, transforming vague specs into structured, test-driven implementation plans for engineers.
AsiaOstrichGenerate plan.json files from specifications, OpenSpec changes, or free-text requirements.
CarbeneAIDispatches fresh subagents per task with spec and quality reviews.
dandawateyCreate isolated Git worktrees for parallel feature branch development.
nschnebleTransform feature specifications into step-by-step implementation plans with Gherkin scenarios.