task

Plans and executes research tasks through structured T-NNN task files and spine commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research work often happens ad hoc, leaving no durable record of what was planned, decided, or produced. This Skill structures substantial work into numbered task files with explicit plans, tracked statuses, and auditable commit history. ## Core Features & Use Cases - Task Planning: Interviews the researcher in batches, allocates a T-NNN identifier, and writes a four-field task file with status planned under docs/tasks/. - Task Execution: Works through plan lines one commit boundary at a time, routing products to their proper homes and appending spine lines per outcome. - Retroactive Capture & Close: Records work done outside a task, flips status to done or killed, and sweeps for decision records and backlog items. - Use Case: A researcher designing a multi-step experiment says "/task plan"; the Skill interviews them, writes docs/tasks/T-007-experiment.md, gets approval, and commits it before any work begins. ## Quick Start Ask the assistant to run /task plan to design and file a new numbered research task before starting the work.

Frequently Asked Questions about task

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

FAQPage Schema
How do I plan a research task with a structured task file?

Invoke /task plan and the Skill reads docs/framing.md, searches the backlog and decision records, then interviews you in batches of three questions. It allocates the next T-NNN number, writes a four-field task file with status planned, and commits it after your approval.

How does task execution track progress across commits?

The execute mode finds the first unfinished plan line, sets status to active, and works to the next commit boundary. Each outcome gets products routed to their homes, a spine line appended, and one commit with explicit paths before pausing for your confirmation.

Can I record work that happened without a task file?

Yes, the retroactive mode allocates a T-NNN number and appends spine lines for durable work done in a free-form session. Single-commit outcomes need no file; multi-commit or paused work gets a file written at close with status done.

What happens when a task is closed or killed?

The close mode flips the status and appends a closing spine line marked done or killed with the outcome. It sweeps the conversation for unrecorded decisions, backlog items, and framing contradictions, then commits the result.

When should I not create a task file?

Skip task files for small single-commit work, which the retroactive mode handles with just a spine line. The planning interview scales to the task, so trivial work does not need the full plan-approve-commit cycle.