Generate step-by-step implementation plans with file paths, code snippets, and commands.
npx skills add https://github.com/ZJUxjy/opencode_lite --skill writing-plans-zjuxjy
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/ZJUxjy/opencode_lite/tree/main/skills/writing-plans Command: npx skills add https://github.com/ZJUxjy/opencode_lite --skill writing-plans-zjuxjy
This Skill addresses the challenge of creating clear, actionable, and comprehensive implementation plans for software development tasks, especially when the engineer has limited context about the codebase or problem domain.
Use the writing-plans skill to create an implementation plan for adding user authentication.
High-intent search queries and answers about installing and using this skill.
To create a detailed implementation plan, break the task into bite-sized steps including exact file paths, code snippets for tests and implementation, and precise execution commands. This assumes an engineer with general skills but no specific project context.
A software implementation plan should include a standardized header, task structure, and frequent commit guidance. It must ensure adherence to TDD, DRY, and YAGNI principles by providing exact code snippets for tests and implementation alongside execution commands.
Yes, you can generate a step-by-step task breakdown without prior codebase context. The plan provides all necessary contextual guidance, assuming an engineer with good general skills but limited domain knowledge to ensure a smooth development process.
The best way to structure a development plan for adding user authentication is to outline every file to touch, provide exact code snippets for tests and implementation, and list precise commands to run, ensuring consistent task breakdown and best practice adherence.
Yes, the generated implementation plan provides exact execution commands and file paths. It delivers bite-sized, actionable steps for implementation, writing tests, and committing changes to guide an engineer through the entire process.
You need a standardized plan format for software implementation when starting a new feature or multi-step task. It ensures all plans include a consistent header, task structure, and adherence to development best practices like DRY, YAGNI, and TDD.
JackiexiaoGenerate step-by-step implementation plans with file modifications and test cases.
Himanshu040604Generate step-by-step implementation plans with file paths, code snippets, and commit messages.
EntroVyxGenerate structured markdown implementation plans with TDD-based steps.
royhenengelGenerate spec-driven implementation plans for software development tasks.
