mcpField
C
create-tasks

create-tasks

github.com/patrickruddimanAgent workflows36 installs
Repository

About create-tasks

A task-generation skill that turns an approved roadmap into bounded task files. It requires design approval, checks dependencies and repository paths, and materializes one ready topological wave at a time while preserving existing task state.

Key features

  1. 01Requires approved design and roadmap
  2. 02Builds a complete task inventory and DAG
  3. 03Verifies paths and reconciles task state
  4. 04Generates bounded batches of task files
  5. 05Preserves consumed tasks and existing IDs

Use cases

  1. 01Create execution tasks from an approved roadmap
  2. 02Resume task generation while preserving repository conventions
  3. 03Add follow-up tasks after changes to consumed work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/patrickruddiman/skills --skill create-tasks

After installing, type/create-tasksin Claude Code to confirm it loaded.

Details

From the project README

Create tasks

Run the task half of roadmap. Design first; task files are the materialized execution view of an approved roadmap.

Workflow

  1. Load ../roadmap/SKILL.md, ../roadmap/references/roadmap-schema.md, and ../roadmap/references/task-generation.md.
  2. Read the named roadmap.md. If only a legacy design or slice exists, use it as source for an adjacent roadmap without reopening settled decisions.
  3. Require explicit design approval and no blocking design questions.
  4. Run Roadmap phases 7-9: complete inventory and DAG, task-boundary approval, path re-verification, state reconciliation, and bounded materialization.
  5. Update tasks/README.md after every batch.

Compatibility and state

  • Preserve existing task IDs and repository naming conventions when resuming.
  • An unconsumed file has no checked item in ## Tasks; it may be updated.
  • A consumed file has at least one checked item in ## Tasks; never edit it.
  • Record design changes affecting consumed work as roadmap amendments and append replacement, migration, or follow-up tasks.

Rules

  • The full task inventory and acyclic DAG exist before detailed task files.
  • Every task is one coherent, independently executable outcome with concrete paths.
  • Every task has code-verifiable acceptance criteria and at least one real test.
  • No code samples, estimates, setup-only tasks, speculative work, or human inspection.
  • Materialize one ready topological wave at a time, capped at 20 files unless the user chooses another cap.

Comments

Markdown supported