task

Define and enforce a scoped workflow for non-bugfix software tasks.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/dohernandez/claude-skills --skill task-dohernandez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/dohernandez/claude-skills/tree/main/plugins/task/skills/task
Command: npx skills add https://github.com/dohernandez/claude-skills --skill task-dohernandez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-bugfix work often suffers from unclear scope, unplanned changes, and poor verification, leading to wasted effort and misaligned outcomes.

Core Features & Use Cases

  • Structured approach to scope, plan, implement, and verify non-bugfix work (features, chores, refactors, docs).
  • Guides teams to produce explicit plans, follow patterns, and validate results with tests.
  • Enables learning from project structure and applying established coding conventions.

Quick Start

Launch the task workflow to start with scope and plan before implementation.

Frequently Asked Questions about task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured workflow for non-bugfix tasks in software engineering?

A structured workflow for non-bugfix work enforces disciplined phases across scope, plan, implement, and verify. It guides teams to produce explicit plans, follow established coding conventions, and validate results with full test checks.

How do I plan and implement new software features without losing scope?

To plan and implement features without losing scope, use a workflow that requires explicit scoping and planning before implementation. This disciplined approach ensures changes are validated with tests, preventing wasted effort and misaligned outcomes.

Can I use this structured workflow for refactoring and documentation tasks?

Yes, you can use this structured workflow for refactoring and documentation tasks. It is explicitly designed to guide planning, execution, and validation for any non-bugfix work, including chores and documentation within software projects.

Does this workflow support test-driven development for new code?

Yes, this workflow supports test-driven development by satisfying verification steps. It ensures full test checks are performed during the implementation phase, guiding teams to validate results and apply established coding conventions.

What is the best way to verify code changes for chores and refactors?

The best way to verify code changes for chores and refactors is to follow a structured workflow that enforces a dedicated verification phase. This ensures full test checks are completed, validating that the implementation meets the explicit plan.