From adlc-team
Break an approved spec into atomic dev tasks. Trigger: 'break [FEAT-ID] into tasks', 'create tasks for', 'task breakdown for'. Guard: spec must be approved.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adlc-team:ba-split-tasksThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<context>
# Check registry for approval
cat .sdlc/specs/[FEAT-ID]-registry.json | python3 -c "
import sys, json
data = json.load(sys.stdin)
approved = data.get('spec_approved_at')
if not approved:
print('BLOCKED: Spec not approved yet. Get BA to approve first.')
sys.exit(1)
print(f'Spec approved at {approved}')
"
If not approved, stop immediately. Do not proceed.
.sdlc/specs/[FEAT-ID]-*-spec.md — the approved spec.sdlc/domain-terms.md — terminologyCLAUDE.md — project structure and stack.sdlc/verification.yml — what gates existFor each task, define:
[FEAT-ID]-T[NNN]: [action verb] [what]Rules:
Group tasks into half-day slices (2-4 tasks per slice):
Within each slice, mark which tasks can run in parallel.
Output to .sdlc/tasks/[FEAT-ID]/task-[NNN].md:
# [FEAT-ID]-T[NNN]: [Title]
## Acceptance Criteria
- AC-[N]: [description from spec]
## Implementation scope
**Files to create:**
- [path]
**Files to modify:**
- [path] — [what changes]
## Test-first approach
Write these tests first (RED):
1. `Test_[Feature]_AC[N]_[Behavior]` — [what it tests]
## Dependencies
- Depends on: [task IDs or "none"]
- Blocks: [task IDs or "none"]
## Complexity: [simple|moderate|complex]
## Verification
Run after implementation:
- post_task gates from verification.yml
Also create slice plan at .sdlc/tasks/[FEAT-ID]/slice-plan.md:
# [FEAT-ID] Slice Plan
## Slice 1: [theme]
| Task | Complexity | Parallel? | Depends on |
|---|---|---|---|
| T001 | simple | yes | none |
| T002 | moderate | yes | none |
| T003 | moderate | no | T001 |
## Slice 2: [theme]
...
Show the slice plan to the user. Wait for approval before creating GitHub Issues.
On approval:
# Create task issues
for each task:
gh issue create --title "[FEAT-ID]-T[NNN]: [title]" \
--body-file .sdlc/tasks/[FEAT-ID]/task-[NNN].md \
--label "adlc:task,adlc:ready" \
--project [PROJECT_NUMBER]
# Update spec issue
gh issue comment [SPEC_ISSUE] --body "## BA: Task breakdown complete — [FEAT-ID]
**Tasks:** [count] tasks in [count] slices
**Ready for DEV:** Pick up via dev-start"
gh issue edit [SPEC_ISSUE] --remove-label "adlc:spec-approved" --add-label "adlc:tasks-ready"
- `.sdlc/specs/[FEAT-ID]-*-spec.md`
- `.sdlc/specs/[FEAT-ID]-registry.json`
- `.sdlc/domain-terms.md`
- `.sdlc/verification.yml`
npx claudepluginhub obacker/claude-code-plugins --plugin adlc-teamGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.