describe-tasks

Generates TASKS.md task registries for described initiatives using repo rules and docs.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill describe-tasks-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: describe-tasks
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/describe-tasks
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill describe-tasks-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a described initiative into an executable, dependency-ordered task list is slow and error-prone when done by hand, especially when repo-specific rules in AGENTS.md, CLAUDE.md, and docs must be respected. This Skill automates the generation of a structured TASKS.md registry grounded in the actual repository context. ## Core Features & Use Cases - Initiative-Aware Task Generation: Loads the initiative folder under docs/described/<slug>/ (master plan, blueprint, decisions, QA notes) before writing any tasks. - Repo Rule Compliance: Treats AGENTS.md, CLAUDE.md, and repo docs as first-class rule sources and surfaces conflicts before generating dependent tasks. - Structured TASKS.md Output: Produces task IDs, statuses, owner lanes, dependencies, acceptance criteria, verification commands, manual QA expectations, and a progress log. - Use Case: After drafting a master plan for a new dashboard feature in docs/described/dashboard-publish/, run /describe-tasks dashboard-publish to get an executable, dependency-ordered TASKS.md that follows the repo's naming and verification conventions. ## Quick Start Ask the assistant to run /describe-tasks followed by your initiative slug to regenerate TASKS.md for that initiative.

Frequently Asked Questions about describe-tasks

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

FAQPage Schema
How do I generate a TASKS.md file for an initiative?▼

Invoke /describe-tasks followed by the initiative slug, for example /describe-tasks dashboard-publish. The Skill loads the initiative folder under docs/described/<slug>/ plus repo rule files, then writes a structured TASKS.md with ordered tasks, acceptance criteria, and verification commands.

What files does the describe-tasks workflow read before generating tasks?▼

It reads the initiative's README.md, master-plan.md, blueprint.md, plan.md, decisions.md, qa.md, and manual-testing.md, plus AGENTS.md, CLAUDE.md, and relevant repo docs. It also inspects source, tests, package scripts, and tooling before finalizing tasks.

What happens if AGENTS.md and CLAUDE.md rules conflict?▼

The Skill treats AGENTS.md, CLAUDE.md, and repo docs as first-class rule sources. If they conflict, it surfaces the conflict before generating any tasks that depend on the disputed rule, rather than silently picking one.

Can describe-tasks implement the tasks it generates?▼

No. The Skill explicitly does not implement product code and does not invent scope beyond the described initiative. It only produces the TASKS.md registry; execution of tasks is a separate step.

What happens if I run describe-tasks without an initiative slug?▼

If the slug is missing, the Skill asks for it before writing any files. It will not guess an initiative or generate a TASKS.md without a valid docs/described/<slug>/ folder to load.