agentsclimarketplace

Divide task

Skill retz8/pastiche/.claude/skills/divide-task

drawing UI consistently with agents, at the top of Design System + Component Library

Install
npx -y skills add retz8/pastiche --skill divide-task

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Divide a specced pastiche task into sub-task GitHub issues with autonomy and dependency labels, mirror them into `_dev/TODO.md`, and update the parent issue. Use after `grill-to-spec` completes for a task, or when the user invokes `/divide-task`.

SKILL.md

1.9 KB, as published. Nobody here has run it

divide-task

Harness conventions: _dev/docs/harness.md. Requires: task spec written, task [WIP], feature branch checked out.

Workflow

  1. Derive sub-tasks from the spec. Each sub-task is one implementation step, sized for a single overnight session. Number them N.1, N.2, … where N is the task's TODO number.

  2. Analyze each sub-task:

    • Autonomy — purely mechanical, mergeable without human judgment → autonomous-ready; otherwise → decision-needed. When in doubt, decision-needed.
    • Dependencies — which sub-tasks must land first. Independent sub-tasks that touch disjoint files/logic may run in parallel; note the execution order.

  3. Review with the user before creating anything: list sub-tasks, labels, and dependency order. Adjust until approved.

  4. Create child issues. For each sub-task:

    • Title [N.x] <name>; body: one-paragraph scope + pointer to the spec path; same milestone as the parent; autonomy label.
    • For blocked ones: create blocked-by-<blocker-issue-number> labels on demand (gh label create) and apply them. Blockers must be created first so their issue numbers exist.
    • Link each as a sub-issue of the parent (GitHub sub-issue, or a task-list in the parent body if unavailable).

  5. Mirror into _dev/TODO.md. Under the task line, add an indented checklist: - [ ] **N.x** <name> (#<issue>).

  6. Update the parent issue. Add the sub-issue links and the spec reference.

Label lifecycle (for whoever completes a sub-task)

When a blocking sub-task closes, remove its blocked-by-<its-number> label from every issue carrying it, and tick the sub-task checkbox in TODO.md.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.