bentz/dev-tasks-skills
Overview
This skill guides complex development tasks end-to-end. It clarifies goals through multi-turn dialogue, then organizes execution into Plans and Runners to produce actionable tasks and todos. The skill enforces safe operations like confirmation for destructive commands and supports archiving flows when requested.
How this skill works
When a user has no specific task id or file path, the skill enters a Plan phase to elicit requirements, constraints, acceptance criteria, and a proposed task breakdown. When a task id or path is provided, it switches to Runner mode to manage execution, update todos, and track progress. It reads reference documents and templates on demand and triggers archiving workflows only when the user explicitly requests archiving.
When to use it
- Scoping a complex feature or epic that needs refined acceptance criteria and a task plan
- Converting high-level requirements into an ordered set of actionable tasks and todos
- Managing execution of a specific task by id or file path with step-by-step tracking
- Requesting safe destructive actions where explicit confirmation is required
- Initiating an archive of task(s) or project artifacts by explicitly asking to archive
Best practices
- Start without a task id to run the Plan flow and confirm the plan before persisting tasks
- Provide task ids or file paths when you want the Runner to take over execution
- Explicitly confirm any destructive commands when prompted to avoid accidental changes
- Request archiving only when ready; the skill follows a defined archive procedure on explicit instruction
- Keep reference needs minimal—the skill reads only required documents and templates on demand
Example use cases
- A product manager supplies high-level goals to get a prioritized task plan and acceptance criteria
- A developer provides a task id to receive step-by-step runner instructions and updated todos
- A team lead asks to archive completed epics; the skill triggers the archive workflow after confirmation
- A contributor requests a safe refactor and the skill asks for explicit confirmation before any destructive step
FAQ
The skill enters the Plan phase to clarify goals and produce a proposed task breakdown; nothing is persisted until you confirm.
How does archiving work?
Archiving runs only when you explicitly request it; the skill follows the archive workflow and policies and will prompt for confirmation if needed.
