Create structured, verifiable task plans for software development projects.
npx skills add https://github.com/achmf/KostaHub --skill plan-writing-achmf
Please help me install this Agent Skill. Skill: plan-writing Source: https://github.com/achmf/KostaHub/tree/main/.agent/skills/plan-writing Command: npx skills add https://github.com/achmf/KostaHub --skill plan-writing-achmf
This skill eliminates ambiguity and scope creep in complex projects by enforcing a structured, verifiable, and actionable planning framework.
Use the plan-writing skill to create a structured task plan for the upcoming user authentication feature implementation.
High-intent search queries and answers about installing and using this skill.
To create a structured task plan for complex software development, break large objectives into 5-10 minute, independently verifiable tasks. This approach enforces clear dependency mapping and outcome-based verification to eliminate ambiguity and scope creep.
The best way to break down a refactoring project is to divide large objectives into 5-10 minute, independently verifiable tasks. This ensures every task has a clear definition of done, preventing incomplete work and identifying critical paths.
Scope creep happens in feature implementation due to ambiguity and untracked dependencies. Prevent it by enforcing a structured, verifiable, and actionable planning framework that maps dependencies and defines clear outcome-based verification criteria for every task.
Yes, you can use minimal task planning for legacy codebase refactoring. It generates a clear roadmap that identifies dependencies and critical paths while providing project-specific documentation without relying on rigid templates.
Yes, structured task planning works for bug fixing workflows by applying clear dependency mapping and outcome-based verification. It ensures every bug fix has a clear definition of done, preventing incomplete work and eliminating ambiguity.
You should not use verifiable task plans for project management when your work does not require clear dependency mapping or outcome-based verification. It is specifically designed for complex software development scenarios like feature implementation and refactoring.
sumik5Decompose high-level project strategies into parallelizable developer tasks.
airclearExecute Conductor track plan tasks sequentially and update documentation.
SandroBeatzManage project issues and tasks with the beads (bd) command-line tracker.
FlorianRiquelmeEnforces standardized conventions for Git commits, documentation, dependencies, and across-project workflows.
