Break down a spec section or milestone into actionable, session-sized tasks. Use when a milestone is too large, when starting implementation, when the user asks to break down work, or when refining task granularity.
Breaks down large spec sections or milestones into atomic, session-sized tasks with file paths and acceptance criteria. Triggers when a milestone is too large, when starting implementation, or when the user asks to break down work.
/plugin marketplace add Someblueman/spec-flow/plugin install someblueman-spec-flow@Someblueman/spec-flowThis skill is limited to using the following tools:
Convert high-level spec sections into atomic, implementable tasks.
Parse from conversation:
Read the relevant context:
- .claude/spec/SPEC.md (requirements for this milestone)
- .claude/spec/tasks/{milestone}.md (existing tasks if any)
- .claude/steering/tech.md (technology constraints)
Extract:
Size Tasks Appropriately:
Make Tasks Independent:
Include Context:
For each task, define:
### N. Task Title (Action-Oriented)
**Status**: Pending
**Files**: `path/to/file.go`, `path/to/test.go`
**Depends**: Task M (if applicable)
**Acceptance**:
- [ ] Specific, verifiable criterion
- [ ] Another criterion
- [ ] Tests pass (if applicable)
For a new feature:
For a refactoring:
For a bug fix:
For an integration:
Write to .claude/spec/tasks/{milestone}.md:
# Tasks: {Milestone Name}
> Implements {REQ-xxx, REQ-yyy} from SPEC.md
## Status: Pending (0%)
## Dependencies
- {Other milestone if blocked}
---
## Tasks
{Generated tasks}
---
## Notes
{Technical notes, open questions}
If this is a new task file:
- [ ] @tasks/{milestone}.md - {Description}Input: "Break down the authentication milestone"
SPEC.md excerpt:
### MVP
- [ ] @tasks/auth.md - Authentication system
Requirements:
Generated tasks/auth.md:
# Tasks: Authentication System
> Implements [REQ-001], [REQ-002], [REQ-003] from SPEC.md
## Status: Pending (0%)
## Dependencies
- None
---
## Tasks
### 1. User Model
**Status**: Pending
**Files**: `internal/user/user.go`, `internal/user/user_test.go`
**Acceptance**:
- [ ] User struct with ID, email, password hash
- [ ] Password hashing with bcrypt
- [ ] Validation for email format
- [ ] Unit tests for validation
### 2. User Repository
**Status**: Pending
**Files**: `internal/user/repository.go`, `internal/user/repository_test.go`
**Depends**: Task 1
**Acceptance**:
- [ ] Create user
- [ ] Find user by email
- [ ] SQL migrations for users table
- [ ] Integration tests with test DB
### 3. Signup Handler
**Status**: Pending
**Files**: `internal/api/signup.go`, `internal/api/signup_test.go`
**Depends**: Task 2
**Acceptance**:
- [ ] POST /signup endpoint
- [ ] Validates email not already taken
- [ ] Returns user ID on success
- [ ] Returns 400 on validation error
### 4. Session Management
**Status**: Pending
**Files**: `internal/session/session.go`, `internal/session/store.go`
**Acceptance**:
- [ ] Session struct with user ID, expiry
- [ ] Create session on login
- [ ] Persist to database
- [ ] Cookie configuration
### 5. Login Handler
**Status**: Pending
**Files**: `internal/api/login.go`, `internal/api/login_test.go`
**Depends**: Task 2, Task 4
**Acceptance**:
- [ ] POST /login endpoint
- [ ] Validates credentials
- [ ] Creates session
- [ ] Sets session cookie
### 6. Auth Middleware
**Status**: Pending
**Files**: `internal/api/middleware/auth.go`
**Depends**: Task 4
**Acceptance**:
- [ ] Validates session cookie
- [ ] Adds user to request context
- [ ] Returns 401 on invalid session
---
## Notes
- Using bcrypt for passwords (not argon2 for simplicity)
- Sessions stored in DB, not Redis (MVP simplicity)
- Cookie httpOnly, secure, sameSite=lax
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.