dev-tasks
/dev-tasks
Use when one or more approved PRDs already exist (from dev-design or otherwise) and you need to generate or refresh the high-level TASKS.md for each — a tracking table plus a short per-task spec, not code. Re-run any time a PRD changes — it regenerates tasks from the current PRD and reconciles an existing tasks file (preserving Status) instead of clobbering it.
- Author
- tejitpabari99 ↗
- Repository
- tejit-plugin ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when one or more approved PRDs already exist (from dev-design or otherwise) and you need to generate or refresh the high-level TASKS.md for each — a tracking table plus a short per-task spec, not code. Re-run any time a PRD changes — it regenerates tasks from the current PRD and reconciles an existing tasks file (preserving Status) instead of clobbering it.
Original author description
Use when one or more approved PRDs already exist (from dev-design or otherwise) and you need to generate or refresh the high-level TASKS.md for each — a tracking table plus a short per-task spec, not code. Re-run any time a PRD changes — it regenerates tasks from the current PRD and reconciles an existing tasks file (preserving Status) instead of clobbering it.
How it works
- Overview
- When to Use
- The Gate: only build tasks from a settled PRD
- Workflow
- Output Convention
- TASKS.md format
- Keeping PRD ↔ tasks in sync
- Common Mistakes
SKILL.md preview
---
name: dev-tasks
description: Use when one or more approved PRDs already exist (from dev-design or otherwise) and you need to generate or refresh the high-level TASKS.md for each — a tracking table plus a short per-task spec, not code. Re-run any time a PRD changes — it regenerates tasks from the current PRD and reconciles an existing tasks file (preserving Status) instead of clobbering it.
metadata:
version: "0.1.0"
---
# dev-tasks — Approved PRD → TASKS.md
Before anything else, follow `../_shared/update-check.md`.
## Overview
Generate each sub-project's `TASKS.md` as a **pure projection of its PRD**: a tracking
table plus a short, high-level spec per task — no code, no exhaustive file lists. Core
principle: **the PRD is the single source of truth; tasks are regenerated from it, never
hand-edited to chase a PRD change**, and the one exception is the tracking table's
**Status** column, which is never regenerated — see below.
Shared dispatch/output conventions live in `../_shared/dev-common.md`.
## When to Use
- A PRD exists (typically from `dev-design`) and you need its tasks.
- A PRD changed and its `TASKS.md` needs refreshing.
- The ask is "generate tasks", "break the PRD into tasks", "update the tasks".
- **Not for:** designing/decomposing an idea (`dev-design`); writing code.
## The Gate: only build tasks from a settled PRD
A PRD's `## Risks / Open Questions` section is the contract. Before generating tasks,
check it:
```dot
digraph g {
"Read PRD Risks / Open Questions" [shape=box];
"Any [OPEN] items?" [shape=diamond];
"STOP: report OPEN items, ask human to resolve in PRD" [shape=box];
"Generate / refresh TASKS.md from current PRD" [shape=box];
"Read PRD Risks / Open Questions" -> "Any [OPEN] items?";
"Any [OPEN] items?" -> "STOP: report OPEN items, ask human to resolve in PRD" [label="yes"];
"Any [OPEN] items?" -> "Generate / refresh TASKS.md from current PRD" [label="no (all RESOLVED/DEFERRED)"];
}
```
**Do not invent answers to `[OPEN]` items to unblock yourself.** Route them back to the
human to record as `[RESOLVED: …]` or `[DEFERRED]` *in the PRD*; tasks then regenerate
deterministically.
**Auto mode** (see Auto mode in `../_shared/dev-common.md`): do not stop. Each `[OPEN]`
item takes the recommended default and is rewritten in the PRD as
`[RESOLVED: auto default - <choice>]`, then tasks are generated.
## Workflow
0. If `auto` is in the request, print the Auto mode text from `../_shared/dev-common.md` first thing, if it has not been printed yet.
1. **Workspace guard.** Apply the Workspace guard in `../_shared/dev-common.md` before
anything else (pull, then a worktree off the latest default branch for new work).
If this is the first dev-loop skill of this piece of work, show once: "Say `auto` any
time to run all remaining stages without stopping."
2. **Locate the PRD(s).** From the human's pointer — a sub-project folder, a branch
folder, or an explicit path. Confirm the set before proceeding (skip in auto mode).
3. **Check the gate (per PRD).** Any `[OPEN]` item → STOP for that PRD, list them, ask the
human to resolve in the PRD (follow Question rules: plain words, a default for each).
Proceed only for settled PRDs. Auto mode: take defaults and continue, as above.
4. **Generate or refresh, per PRD.** Dispatch one sub-agent per settled
PRD, in parallel, using `tasks-agent-prompt-template.md`. Each agent reads the whole
PRD (esp. Architecture, Decisions, Risks / Open Questions) and:
- No `TASKS.md` exists → author it fresh, every task `Status: todo`.
- `TASKS.md` exists → **reconcile**: add/modify/remove only tasks affected by what
changed in the PRD; **preserve the `Status` value of every task that still exists**,
even if its description text changes; report a short diff. Never blind-overwrite.
5. **Verify + report.** Confirm each `TASKS.md` exists and covers tests (Test policy) and
CI (CI default); relay each agent's change summary.
6. **Hand off.** Write the Handoff section per `../_shared/dev-common.md` (stage: tasks
done; next: `dev-code`) and end with its "Continue here" message. In auto mode write
the file, skip the message, and run `dev-code` next.
## Output Convention
```
docs/agent_files/<branch-slug>-<YYYYMMDD-HHMM>/<NN-kebab-name>/TASKS.md (sibling of PRD.md)
```
## TASKS.md format
Length: aim for **~60–150 words per task** (soft target — going over is fine; never trim
after writing). No code, no exhaustive file list — that's for the coding agent to find via
the PRD + its own exploration (see `dev-code`).
```markdown
---
status: draft
summary: <one line>
date: <YYYY-MM-DD>
---
# Tasks: <title>
Source of truth: <PRD path>. <1–3 sentences.>
| # | Task | Depends on | Status |
|---|---|---|---|
| 1 | <short name> | none | todo |
| 2 | <short name> | 1 | todo |
## Task 1 — <short name>
What it is / what it means: <1–2 sentences>.
What changes at a high level: <components/areas/behaviors touched — not a file list>.
Done when: <observable, checkable acceptance criteria, including the tests that prove it>.
## Task 2 — <short name>
...
```
**Mandatory in every TASKS.md:**
- **Tests (Test policy).** Test coverage is never optional: either a dedicated test task,
or explicit tests named in each task's Done-when. `dev-code` writes them test-first.
- **CI (CI default).** If the repo has no CI workflow that runs the tests on push/PR
(look in `.github/workflows/`), add a task to wire one in (e.g.
`.github/workflows/ci.yml`), so CI exists when the branch is pushed.
## Keeping PRD ↔ tasks in sync
Resolved an Open Question? Record it in the PRD as `[RESOLVED: …]`, then **re-run
`dev-tasks`** — don't hand-edit `TASKS.md`. Task descriptions are disposable/regenerable
from the PRD; Status is the one exception (operational state, not design projection) and
survives every regeneration. Re-runs reconcile and report a diff.
## Common Mistakes
- **Generating tasks past the gate.** `[OPEN]` items block; route them back, don't guess.
- **Blind overwrite, or losing Status, on reconcile.** Preserve unaffected tasks and Status.
- **Adding scope.** Tasks only implement what the PRD decides.
- **Code or an exhaustive file list in a task.** That's `dev-code`'s job at implementation
time, grounded in the PRD + its own repo exploration.
- **Setting Status to anything but `todo` here.** Only `dev-code` moves it further.
- **Tasks without tests, or no CI task when the repo has no CI.** Both are mandatory.
- **Designing here.** No decomposition or new architecture — that's `dev-design`.
Files in this package (2)
- SKILL.md 6 KB
- tasks-agent-prompt-template.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tejitpabari99/tejit-plugin | 100 | MIT |
| alecs5am/ralphy | 87 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 360283da2968 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100dev-design
Use when given a large, multi-part feature/refactor/initiative idea (often a pasted proposal or brain-dump) that needs to be understood, questioned, and broken into sub-projects, each captured as a PRD (a short PM-spec + architecture doc, design only). Stops at approved PRDs;… - 100dev-code
Use for ALL coding work, with or without a PRD. With an approved design+tasks folder (PRD.md + TASKS.md from dev-design/dev-tasks), executes the tasks via coding sub-agents in dependency order, one commit per task, with the orchestrator tracking each task Status in TASKS.md.… - 100tasks-generator
Generate sprint-based development tasks from a PRD. Use when asked to create tasks or break down requirements. Don't use for PRD/TAD authoring or task execution. - 84prd
Guide the user through writing a Product Requirements Document or feature spec. Uses a four-phase gated flow (Discovery → Specify → Plan → Tasks) to produce spec.md, plan.md, and tasks.md in the project's planning/prd/ directory. Use when the user says "write a PRD", "write a… - 100tasks
基于可用的设计文档为功能特性生成可执行的、按依赖关系排序的 tasks.md。在用户要求生成任务列表、制定实施计划、从 spec/design 产出 tasks 时使用。 - 100ralph-prd
Generate a Ralph backlog for a new feature. Use when planning a feature, starting a new project, or when asked to create tasks. Triggers on: create tasks, write prd for, plan this feature, requirements for, spec out, generate TODO-next.md, use the ralph-prd skill.