From adlc-solo
Break a milestone into implementation slices and tasks. Use after spec is approved to plan the dev work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adlc-solo:plan-sliceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Decompose an approved milestone spec into implementation slices and atomic dev tasks.
Decompose an approved milestone spec into implementation slices and atomic dev tasks.
Each task must be:
For each task, specify:
Task [N]: [Title]
- Files: [exact paths to create or modify]
- ACs covered: [AC IDs]
- Test names: Test_[Feature]_AC[N]_[Behavior]
- Dependencies: [task IDs this depends on, or "none"]
- Parallel: [yes/no — can run simultaneously with other tasks in same slice]
- Estimated complexity: simple (≤2 files) | moderate (3-5 files) | complex (6+ files)
- Model recommendation: haiku (simple) | sonnet (moderate) | opus (complex/architectural)
Group tasks into slices (each slice = half-day of work):
Write to .sdlc/milestones/[MILESTONE-ID]/slice-plan.md:
# Slice Plan: [Milestone Title]
## Slice 1: [Description]
Estimated: [X hours]
### Task 1.1: [Title]
- Files: src/models/user.ts (create), src/models/user.test.ts (create)
- ACs: AC1, AC2
- Tests: Test_Auth_AC1_ValidLogin, Test_Auth_AC2_InvalidPassword
- Dependencies: none
- Parallel: yes
- Model: sonnet
### Task 1.2: [Title]
...
## Slice 2: [Description]
Depends on: Slice 1
...
Present to user for approval before implementation begins.
npx claudepluginhub obacker/claude-code-plugins --plugin adlc-soloProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.