mcpField
D
do-status

do-status

github.com/fabio-barbozaDevelopment3075 installsUpdated today
Repository

About do-status

do-status is an agent skill for checking PRD task progress and producing status reports in Brazilian Portuguese. It locates PRDs by directory convention, identifies the next pending task, and can check review-file completeness.

Key features

  1. 01Find PRDs using the prd-* convention
  2. 02Parse completed and pending tasks
  3. 03Identify the next task and dependencies
  4. 04Optionally check review-file integrity
  5. 05Produce Brazilian Portuguese reports

Use cases

  1. 01Review progress on a feature PRD
  2. 02Determine the next actionable task
  3. 03Find missing task review files

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-status

After installing, type/do-statusin Claude Code to confirm it loaded.

Details

From the project README

Status Report

Directory Convention

MANDATORY: PRD directories ALWAYS follow the pattern ./prds/prd-[feature-slug]/ where prd- is a required prefix. Example: feature user-auth → directory ./prds/prd-user-auth/. When scanning ./prds/, only consider folders matching the prd-* pattern.

Procedures

Step 1: Identify Target PRD

  1. If the user did not provide [feature-slug], scan ./prds/ for folders matching prd-*.
  2. If only one prd-* folder exists, use it automatically. If multiple exist, select the most recently modified.
  3. If ./prds/ does not exist or contains no prd-* folders, halt: "No PRDs found — run do-create-prd first."

Step 2: Read Tasks

  1. Read ./prds/prd-[feature-slug]/tasks/tasks.md. If it does not exist, halt: "tasks.md not found — run do-create-tasks first."
  2. Parse all tasks: [x] = completed, [ ] = pending.
  3. Identify the next pending task (first [ ] in order).
  4. Check if the next pending task has unmet dependencies (any prior task still [ ]).

Step 3: Check Artifact Integrity (Optional)

  1. For each task marked [x], verify its review file exists at ./prds/prd-[feature-slug]/tasks/[num]_task_review.md.
  2. Flag any [x] task missing its review file as incomplete.
  3. If the next pending task is currently in progress, read ./prds/prd-[feature-slug]/tasks/[num]_task.md to show subtask-level progress.

Step 4: Output Status Report

Produce a concise report in this format:

📦 [Feature Name] (prd-[slug])

Progresso: X/Y tasks concluídas (Z%)

✅ Concluídas: 1, 2, 3
⏳ Próxima:    4 — [título da task]
⏸️  Pendentes: 5, 6, 7 ... Y

⚠️  Artefatos ausentes: [lista de tasks [x] sem review file, se houver]
🚫 Bloqueios: [tasks com dependências não atendidas, se houver]

Output Language

Report in Brazilian Portuguese (PT-BR).

Error Handling

  • If ./prds/ does not exist or contains no prd-* folder, halt with: "No PRDs found — run do-create-prd first."
  • If tasks.md does not exist for the selected PRD, halt with: "tasks.md not found — run do-create-tasks first."
  • If multiple prd-* folders exist and none was specified, select the most recently modified — never block on user input.
  • If a task is marked [x] but its review file is missing, list the inconsistency under "Artefatos ausentes" — do not modify any file.

References

  • Tasks index: ./prds/prd-[feature-slug]/tasks/tasks.md
  • Task files: ./prds/prd-[feature-slug]/tasks/[num]_task.md

Comments

Markdown supported