// Create implementation tasks for a requirement. Use when breaking down a REQ, "add task to REQ-001", "create work items", or after approving a requirement. Do NOT use for creating requirements (use req-new instead) or reviewing task status (use sdlc-status instead).
Audit documentation coverage against common user questions. Generates a Q&A matrix, searches docs/code for answers, flags gaps, and creates DRs for missing content. Use when asked to "audit docs", "check documentation coverage", "what questions can users answer", or before releases/demos.
Review and help prepare a contributor's pull request (upstream or fork). Use when the user asks to review a PR, get a contributor PR ready, update a contributor's branch, or ensure a PR meets project standards before merge. Follow this skill so contributor PRs are reviewed consistently and avoid rework (lint/test failures, outdated base, weak description).
Prepare and submit a pull request for the APME project. Syncs with upstream, creates a feature branch, runs quality gates (tox -e lint, tox -e unit), updates documentation and ADRs as needed, commits with conventional commits, then creates the PR via gh. Use when the user asks to submit, create, or open a pull request, or says "submit PR", "open PR", "create PR", "new PR".
Guide for handling pull request reviews, including automated (Copilot) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.
Align branch name with artifact ID when they mismatch. Use when: renumbering a REQ/DR/ADR after branch creation, "branch name is wrong", "rename branch to match", or when PR review flags branch/artifact mismatch. Handles the git branch rename and remote update.
Reference for running lint, test, build, and pod commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use.
| name | task-new |
| description | Create implementation tasks for a requirement. Use when breaking down a REQ, "add task to REQ-001", "create work items", or after approving a requirement. Do NOT use for creating requirements (use req-new instead) or reviewing task status (use sdlc-status instead). |
| argument-hint | [REQ-NNN] [Task Name] [--from-criteria] [--batch] |
| user-invocable | true |
| metadata | {"author":"APME Team","version":"1.0.0"} |
Create implementation tasks for a requirement.
If $ARGUMENTS is provided, parse for:
REQ-NNN → target requirement--from-criteria → generate tasks from acceptance criteria--batch → create multiple tasks in sequence/task-new # Prompt for REQ
/task-new REQ-001 # Create task for specific REQ
/task-new REQ-001 "Task name" # Quick mode with name
/task-new REQ-001 --from-criteria # Generate from acceptance criteria
/task-new REQ-001 --batch # Create multiple tasks
If no REQ specified, list available:
| REQ | Feature | Status | Tasks |
|-----|---------|--------|-------|
| REQ-001 | Scanner | In Progress | 2 |
| REQ-002 | Rewriter | Draft | 0 |
Which REQ? (number)
Read parent requirement to understand context and acceptance criteria.
If REQ has acceptance criteria:
REQ-001 has 4 acceptance criteria. Generate tasks from these? (Y/n/select)
If Y: Generate one task per criterion with placeholder steps. If select: Let user pick which criteria to generate tasks for.
Scan .sdlc/specs/REQ-NNN-*/tasks/TASK-*.md for highest number in this REQ, increment.
Task numbers are per-REQ (REQ-001 has TASK-001, TASK-002; REQ-002 has its own TASK-001).
Task name and description?
Accept: "Name - description" or ask description separately.
Implementation steps (numbered list):
Accept freeform numbered list. Parse into steps array.
Files to create/modify (path: action - purpose):
Accept freeform. Parse into table with path, action (create/modify), purpose.
Prerequisites? (other TASKs, or "none")
Verification steps?
Accept: "tox -e lint, tox -e unit" or freeform list. Always use tox envs (ADR-047).
Which acceptance criteria? (numbers from REQ)
Show AC list from parent REQ, accept numbers.
If task has >6 steps or >5 files:
This task has N steps and M files - larger than ideal (1-2 hours).
Consider splitting? (Y/n)
If Y: Help split into smaller tasks.
Create .sdlc/specs/REQ-NNN-slug/tasks/TASK-NNN-task-slug.md using template.
Slug: 2-4 words, lowercase, hyphens.
Fill:
Done!
- Created: REQ-001-scanner/tasks/TASK-001-ari-wrapper.md
- Status: Pending
- Addresses: AC 1, 3
Create another task for REQ-001? (Y/n)
If Y: Loop back to step 4.
With inline parameters:
| Provided | Skip |
|---|---|
| REQ number | REQ selection |
| Task name in quotes | Name prompt |
--from-criteria | All prompts (generate from AC) |
--batch | Continue prompt (auto-continue) |
With --from-criteria:
With --batch:
Steps — accept:
1. Create module
2. Add parse method
3. Write tests
or
- Create module
- Add parse method
- Write tests
Files — accept:
src/module.py: create - main implementation
tests/test_module.py: create - tests
src/existing.py: modify - add import
Parse into structured table.
| Situation | Handling |
|---|---|
| REQ has no acceptance criteria | Skip AC reference, note in task |
| Tasks directory doesn't exist | Create it |
| Task seems too large | Offer to split |
| No prerequisites | Set to "None" |