simplify-task

Reduce an existing task file to the smallest plan that still delivers its brief.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill simplify-task-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify-task
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/simplify-task
Command: npx skills add https://github.com/toderian/project_template --skill simplify-task-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Task files in docs/tasks_manager/_todos/ often accumulate speculative phases, redundant acceptance criteria, and placeholder sections that make them too large to execute cleanly. This Skill trims an existing task down to the smallest plan that still satisfies its brief, without losing any work the user actually asked for. ## Core Features & Use Cases - Item classification: Every phase checklist item and acceptance criterion is classified as cut, defer, merge, or keep, each with a checkable reason. - Approval-gated rewrite: Shows before/after counts, the full classification table, and a diff of the phases and criteria sections, then stops for approval before rewriting the file. - Deferred work capture: Deferred items are recorded under a Follow-ups section (or as inbox captures) so nothing is silently dropped, and the execution log and ledger stay in sync. - Use Case: A task fails the small-mode gate of execute-plan by a small margin; run this Skill to merge phases sharing files and tests, cut template-driven padding, and get the task back onto the small rung. ## Quick Start Ask the agent to simplify task AUTH-001 because it is too big, then review the proposed diff and approve the rewrite.

Frequently Asked Questions about simplify-task

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

FAQPage Schema
How do I simplify a task file that is too big to execute?

Run the simplify-task skill on the task ID; it reads the task and its git history, classifies every phase item and criterion as cut, defer, merge, or keep, then shows counts and a diff for approval before rewriting the file.

What happens to work that gets cut or deferred from a task?

Cut items are removed with a documented reason, while deferred items are never lost: they are recorded under a Follow-ups section in the task, or captured as inbox items when the repo uses the inbox convention.

Can I simplify an archived or completed task?

No. The task must exist and be in open or in_progress status; archived tasks are never simplified. Phases already ticked off and the execution log are also left untouched.

What if nothing in the task can be cut?

If every item classifies as keep, the skill replies "Lean already." with the counts and stops. It does not manufacture cuts just to shrink the file.

Does simplifying a task affect its run state for execution?

Yes. If a _runs/<ID>/state.md file exists, its phase rows no longer match after simplification; the skill leaves a note there and tells you to re-run at task run-state init <ID> --force before executing.