add-task

Creates area-prefixed task files with briefs, phases, and acceptance criteria in a docs-based task ledger.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a clear work request into a well-structured, trackable task file is repetitive and error-prone: IDs must be reserved, areas and prefixes assigned, duplicates checked, and acceptance criteria kept testable. This Skill standardizes that process so every task lands in docs/tasks_manager/_todos/ with the right shape and passes ledger validation. ## Core Features & Use Cases - Structured task creation: Reserves an area-prefixed task ID, then writes metadata, a brief, phases with checklists, and observable acceptance criteria following the todo convention. - Duplicate and overlap detection: Runs a discovery scan across the inbox, active and archived tasks, roadmap, ledgers, and code before filing anything new. - Spec and design sections: Adds Specification and Design sections plus Spec refs when acceptance criteria alone would lose intent, and can make an existing task implementation-ready. - Roadmap scheduling: Optionally places the task under Urgent, Now, Next, Later, or Someday horizons with milestone targets, then syncs and validates the ledger. - Use Case: You tell the agent "add a task to add rate limiting to the API" and it checks for duplicates, reserves an ID like API-F-003, writes the brief, phases, and criteria, runs at ledger sync && at ledger check, and reports the path. ## Quick Start Ask the agent to add a task for the work you have in mind, for example by saying "add a task to refactor the billing webhook handler with priority high".

Frequently Asked Questions about add-task

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

FAQPage Schema
How do I create a task in the docs/tasks_manager ledger?

Ask the agent to add a task describing the work. The skill checks for duplicates, assigns an area and prefix from _areas.md, reserves an ID with `at reserve task`, writes the brief, phases, and acceptance criteria, then runs `at ledger sync` and `at ledger check`.

When should I use add-task instead of capture-idea?

Use add-task when the request is actionable and clear enough to commit to the backlog. Vague, low-context thoughts belong in the inbox through capture-idea, and oversized work with no visible path belongs in wayfinder.

Does add-task require any setup before first use?

Yes, the repository must already contain a `docs/tasks_manager/` directory, which is created by running `at init --with-tasks`. Without that prerequisite the skill cannot reserve IDs or sync the ledger.

Can add-task set deadlines or target dates on tasks?

Only when the user gives explicit scheduling intent. The skill never asks for dates on its own; goal-level timing is added as a Milestone heading with a target or deadline date inside a roadmap horizon.

What happens if the task already exists or overlaps with other work?

The skill runs a discovery scan across the inbox, active and archived tasks, roadmap, ledgers, and relevant code. If a match is found it reports the existing item and asks whether to append detail, link it, or create a distinct task.

When should a task include Specification and Design sections?

Add them when acceptance criteria alone would lose intent, such as public interfaces, data changes, multiple plausible designs, or open architecture questions. Routine tasks should stay with the core shape only.