SkillsAdd

fabio-barboza/development-orchestrator

do-status

Shows current progress of a PRD — completed tasks, next pending task, completion percentage, and missing artifacts.

First seen Apr 8, 2026

Installation

$ npx skills add fabio-barboza/development-orchestrator --skill do-status
View on skills.sh ↗ GitHub repository ↗

Summary

  • Shows current progress of a PRD — completed tasks, next pending task, completion percentage, and missing artifacts.
  • Use when the user asks for status, progress, what's next, or wants to resume work on a feature.
  • Read-only skill — does not modify any files.
  • Do not use for task implementation, review, or QA.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from fabio-barboza/development-orchestrator · top by installs.

npx skills add fabio-barboza/development-orchestrator
do-execute-task 61 do-create-techspec 58 do-setup 55 do-execute-qa 55 do-execute-review 54 do-create-tasks 54 do-shared 52 do-execute-review-fix 51 do-execute-qa-bugfix 51 do-create-prd 41

Browse all from fabio-barboza/development-orchestrator

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 28
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,874 B
  • docs SUMMARY.md 328 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 54 installs

SKILL.md

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]taskreview.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