do-status
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
- If the user did not provide
[feature-slug], scan./prds/for folders matchingprd-*. - If only one
prd-*folder exists, use it automatically. If multiple exist, select the most recently modified. - If
./prds/does not exist or contains noprd-*folders, halt: "No PRDs found — rundo-create-prdfirst."
Step 2: Read Tasks
- Read
./prds/prd-[feature-slug]/tasks/tasks.md. If it does not exist, halt: "tasks.md not found — rundo-create-tasksfirst." - Parse all tasks:
[x]= completed,[ ]= pending. - Identify the next pending task (first
[ ]in order). - Check if the next pending task has unmet dependencies (any prior task still
[ ]).
Step 3: Check Artifact Integrity (Optional)
- For each task marked
[x], verify its review file exists at./prds/prd-[feature-slug]/tasks/[num]_task_review.md. - Flag any
[x]task missing its review file as incomplete. - If the next pending task is currently in progress, read
./prds/prd-[feature-slug]/tasks/[num]_task.mdto 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 noprd-*folder, halt with: "No PRDs found — rundo-create-prdfirst." - If
tasks.mddoes not exist for the selected PRD, halt with: "tasks.md not found — rundo-create-tasksfirst." - 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
More from fabio-barboza/development-orchestrator
do-execute-task
Implements feature tasks by loading required skills, reading PRD/TechSpec context, analyzing dependencies, executing the implementation with tests, and performing an automatic code review. Marks tasks as complete in tasks.md. Use when the user asks to implement a task, execute a task, or start working on a specific task number. Do not use for creating tasks, running QA, or bug fixing.
35do-create-techspec
Creates Technical Specifications from existing PRDs, translating product requirements into architectural decisions and implementation guidance. Performs deep project analysis, uses Context7 MCP for technical research and Web Search for business rules. Use when the user asks to create a tech spec, define architecture, or plan implementation for a feature with an existing PRD. Do not use for PRD creation, task breakdowns, or direct code implementation.
34do-setup
Initializes the project, identifies relevant skills, and updates the project configuration file (CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/project.mdc, or .cursorrules) with project summary, conventions, and available skills. Accepts an optional argument "agents" to only install orchestration agents and commands without running the full setup. Use when the user asks to initialize the project, configure the agent-assisted development environment, or install agents with "/do-setup agents". Do not use for PRD creation, task implementation, code review, or QA testing.
32do-execute-qa
Validates feature implementation against PRD, Tech Spec, and Tasks through E2E testing via available MCP tools, accessibility verification (WCAG 2.2), and visual analysis. Documents all bugs found with screenshot evidence and generates a comprehensive QA report. Use when the user asks to run QA, validate a feature, or test implementation completeness. Do not use for code review, bug fixing, or task implementation.
32do-create-tasks
Converts PRD and Tech Spec into a detailed, sequenced list of implementation tasks. Each task is a functional, incremental deliverable with its own test suite. Outputs tasks.md and individual task files. Use when the user asks to create tasks, break down work, or plan implementation from an existing PRD and Tech Spec. Do not use for PRD creation, tech spec creation, or actual code implementation.
31do-execute-review
Performs comprehensive code review by analyzing git diff, verifying conformance with project rules, validating test suites, and checking adherence to Tech Spec and Tasks. Generates a structured code review report with severity-classified findings. Use when the user asks for a code review, wants to validate code quality, or needs pre-merge verification. Do not use for QA testing, bug fixing, or task implementation.
31