Generate structured implementation plans with file paths, tests, and commits.
npx skills add https://github.com/kslhunter/simplysm --skill sd-plan
Please help me install this Agent Skill. Skill: sd-plan Source: https://github.com/kslhunter/simplysm/tree/main/.claude/skills/sd-plan Command: npx skills add https://github.com/kslhunter/simplysm --skill sd-plan
Plans for software work are often missing structure or rely on tribal knowledge. This skill provides a complete, repeatable template to capture every task, file touchpoint, test, and commit required to implement a feature.
Draft a complete implementation plan for a new feature and save it to docs/plans/YYYY-MM-DD-<feature-name>.md.
High-intent search queries and answers about installing and using this skill.
Structure a multi-step implementation plan by using a document header, bite-sized tasks, explicit file paths, and commands. This provides a repeatable format to capture every task, file touchpoint, test, and commit required to implement a software feature.
Document file changes and testing steps by generating a plan document that explains what to touch, why, and how to verify changes. This standardizes planning across teams so new features can be consistently implemented and reused.
Break down software development tasks by dividing work into bite-sized steps with precise file paths, commands, and acceptance criteria. This ensures each task includes explicit file touchpoints, testing steps, and commits for comprehensive implementation tracking.
Yes, this implementation planning approach works without external dependencies. It provides a complete, repeatable template to capture every task, file touchpoint, test, and commit required to implement a feature without relying on external tooling or platforms.
Yes, you can standardize implementation plans across multiple engineering teams. This approach enforces an exact plan structure with a document header and bite-sized tasks, ensuring new features are consistently implemented and documented for plan reuse.
Save and organize generated software feature plans by saving them to docs/plans/YYYY-MM-DD-<feature-name>.md. This documentation-driven approach ensures plans explaining what to touch, why, and how to verify changes are consistently stored and accessible.
BermudaLocalsGenerate task-by-task implementation plans with exact file paths and commands.
doitianGenerate bite-sized implementation tasks with file paths, tests, docs, and commits from a spec.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
nguyenthienthanhFetch JIRA ticket details and update statuses from conversation.
