Turn approved spex requirements into specs/NNN-slug/tasks.yaml — approach, boundaries, a design block (modules, entities, decisions) and one task record per agent run with write allowlists, context, signatures and named values, never a person as an actor — make it pass spex check with full coverage, then have a test-analyst subagent add a test for every task to tests.yaml. Use when the user says "tasks", "spex tasks", "plan the tasks", "write the tasks", or after spex approve.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# spex tasks
`SPEX` = `node ${CLAUDE_PLUGIN_ROOT}/scripts/spex.mjs`, from the repo root. Every finding
has a `fix` text; read it.
You are the analyst: you write the claim (`done_when`). You never write its proof:
`tests.yaml` is the test analyst's file, and you do not open it.
## Steps
1. `SPEX gate tasks <dir>`. If it is refused, report what it wants (approval, an open
question, an unknown without a decision) and stop. Open with `nothing to add`: every
record has a task; say so and go to step 9. Open with `… have no test`: go to step 8.
A changed `tasks.yaml` goes back to a person.
2. Read `<dir>/requirements.yaml` once. Then `SPEX show <dir> --inherited` when `spec.md`
names `depends_on`: the decisions, entities and produced signatures of the steps this
one builds on. Use those names exactly, and `consumes` them instead of reading their
folders. Then read only the code the records touch: the module behind each interface,
the test harness conventions, the contract files. Read `.spex/config.yaml` for
`limits`, `live` and `people`. Read `spec.md` only for its Decisions and Alternatives
sections, when a record's `rationale` points there.
…
The line at the top of this page pins the label git:20261107.629412d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_gaixebf6tcos6fsk
GET https://markdownregistry.com/api/v1/resolve?ref=lukaskellerstein/claude-my-marketplace/tasks
GET https://markdownregistry.com/api/v1/blob/82d2602131cd281a2ea8267fb4496022be191e5680c2ca04b2507c3579ac3b97
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
lukaskellerstein/claude-my-marketplace · _archive/paperclip-plugin/skills/infrastructure-planning/SKILL.md · Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub…
lukaskellerstein/claude-my-marketplace · _archive/paperclip-plugin/skills/work-planning/SKILL.md · Design the complete work hierarchy for a Paperclip company — Goals, Projects, and Tasks as a unified top-down planning…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-app-prep/SKILL.md · Gets a project into a demo-worthy, deterministic state before recording — boots the app, seeds realistic data, bypasses…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-assembly/SKILL.md · Assembles measured clips and narration into a finished demo video — reconciles real durations into a timeline, then…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-capture/SKILL.md · Records demo video clips by driving a running app — one clip per storyboard section, with human-feeling pointer motion…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-graphics/SKILL.md · Dresses the Final Cut Pro finish of a demo video with Motion templates — MotionVFX DesignStudio elements downloaded…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-review/SKILL.md · Quality-checks a rendered demo video before it ships — extracts frames, grades each section against its…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-scripting/SKILL.md · Turns a codebase into a demo narrative that has value — picks which capabilities earn screen time, structures them into…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-video/SKILL.md · Orchestrates building a narrated demo video of a project — reads the codebase, writes a storyboard, prepares…
lukaskellerstein/claude-my-marketplace · plugins/demo-video-plugin/skills/demo-voiceover/SKILL.md · Generates demo narration with the ElevenLabs MCP server — one audio file per storyboard section, measured so the editor…
agentii-ai/agentii-investment-intelligence · plugins/vertical-plugins/scenarios/skills/agentii/tasks/SKILL.md · Decompose the plan into research tasks — one task per ticker × skill × mode, grouped by pillar, [P]-marked by the…
papadopouloskyriakos/agentic-chatops · bootstrap-pack/.claude/skills/tasks/SKILL.md · Phase E of greenfield project bootstrap. Atomize design.md + contracts into tasks.json with files_owned + dependencies…
pioneerdotai/pioneer · resources/skills/pioneer/tasks/SKILL.md · Use this skill when Pioneer should create, inspect, update, reschedule, pause, resume, finish, cancel, troubleshoot, or…
cryndoc/polisade-orchestrator · skills/tasks/SKILL.md · Decompose a PLAN / SPEC / FEAT / BUG / DEBT / CHORE into atomic TASK-NNN items ready for the implement flow, via a…
ananthanandanan/skills · skills/engineering/tasks/SKILL.md · Turn an approved SPEC.md into a complete TASKS.md (phases, parallel tracks, dependency map), then create matching…
