Purpose
Manage complete task lifecycle from initial definition through implementation to review and completion. Provides state-based workflow with automated transitions, intelligent task discovery, quality gates, and framework-aware implementation patterns.
Tip: For smoother workflow without permission prompts, consider adding ["Read", "Write", "Edit", "Glob", "Bash", "TodoWrite"] to dangerouslySkipPermissions in your project's .claude/settings.json.
Variables
TASK_ID_PREFIX: TASK # Project prefix for task IDs (TASK, BROOKLY, JIRA, etc.)
TASK_ID_START: 1 # Starting number for new task sequences
TASK_ID_PADDING: 3 # Number of digits for task IDs (3 = 001, 006, 042)
TASK_DIR: ./tasks # Directory where task files are stored
TASK_FILE_FORMAT: {prefix}-{id} [{state}] ({category}): {slug}.md # Filename template
STATE_INITIAL: toRefine # First state after task creation
STATE_READY: toImplement # Requirements refined, ready for coding
STATE_REVIEW: toReview # Implementation complete, needs review
STATE_COMPLETE: done # Fully finished and approved
ENABLE_LINT: true # Run linting during implement/review workflows
ENABLE_TYPECHECK: true # Run type checking validation
ENABLE_BUILD: true # Run build verification
ENABLE_TESTS: true # Run test suite execution
ENABLE_SECURITY_SCAN: false # Run security vulnerability scanning
AUTO_DETECT_FRAMEWORK: true # Automatically detect project framework
DEFAULT_FRAMEWORK: generic # Fallback framework if detection fails
SUPPORTED_FRAMEWORKS: generic, nextjs, django, react, python # Currently supported
COMMIT_STYLE: conventional # Commit message convention (conventional, angular, custom)
Workflow
Parse User Request
- Identify workflow command intent from user input
- Commands: "define task", "refine task", "implement task", "review task"
- Extract task identifier if provided (ID, keywords, category)
- Example: "define task: add user authentication" → Intent: define, Description: "add user authentication"
Determine Workflow Phase
- IF: "define" OR "create" OR "new task" → Route to Define workflow
- IF: "refine" OR "clarify" OR "interview" → Route to Refine workflow
- IF: "implement" OR "code" OR "build" → Route to Implement workflow
- IF: "review" OR "check" OR "validate" → Route to Review workflow
- Example: "refine task 006" → Phase: refine, Task ID: 006
Detect Project Framework
- IF: AUTO_DETECT_FRAMEWORK is true → Scan for framework indicators
- Check for: package.json (Node.js), requirements.txt (Python), go.mod (Go)
- Analyze dependencies and config files to determine specific framework
- Example: package.json with "next" dependency → Framework: nextjs
Route to Cookbook
- Based on workflow phase and detected framework
- Define workflow: cookbook/define.md (framework-agnostic)
- Refine workflow: cookbook/refine.md (framework-agnostic)
- Implement workflow: cookbook/implement/{framework}.md (e.g., generic.md, nextjs.md)
- Review workflow: cookbook/review/{framework}.md (e.g., generic.md, nextjs.md)
- Example: Phase=implement + Framework=nextjs → cookbook/implement/nextjs.md
Execute Workflow
- Load appropriate cookbook workflow
- Follow workflow steps with current Variables configuration
- Use TASK_DIR, TASK_ID_PREFIX, and other Variables throughout
- Apply quality gates if ENABLE_* variables are true
- Example: Execute implement workflow using TASK-006, run lint+typecheck+build+test
Report Results
- Summarize workflow execution
- Show task state transitions (if applicable)
- List files created/modified
- Display next steps in workflow
- Example: "Task TASK-006 transitioned from [toImplement] to [toReview]. Run review workflow next."
Cookbook
Define Task Workflow
- IF: User wants to create new task specification
- THEN: Read and execute:
.claude/skills/task-workflow/cookbook/define.md
- EXAMPLES:
- "define task: add user authentication"
- "create new task for fixing navigation bug"
- "new task: implement dark mode"
Refine Task Workflow
- IF: User wants to clarify task requirements
- THEN: Read and execute:
.claude/skills/task-workflow/cookbook/refine.md
- EXAMPLES:
- "refine task 006"
- "clarify requirements for TASK-006"
- "interview me about the authentication task"
Implement Task Workflow
- IF: User wants to implement task
- THEN: Detect framework, Read and execute:
.claude/skills/task-workflow/cookbook/implement/{framework}.md
- Framework detection: generic (default), nextjs, django, react, python
- EXAMPLES:
- "implement task 006" → cookbook/implement/generic.md (default)
- "implement task 006" (in Next.js project) → cookbook/implement/nextjs.md
- "build TASK-006" → framework-aware routing
Review Task Workflow
- IF: User wants to review task
- THEN: Detect framework, Read and execute:
.claude/skills/task-workflow/cookbook/review/{framework}.md
- Framework detection: generic (default), nextjs, django, react, python
- EXAMPLES:
- "review task 006" → cookbook/review/generic.md (default)
- "review task 006" (in Next.js project) → cookbook/review/nextjs.md
- "validate TASK-006" → framework-aware routing
1---2name: task-workflow-manager3description: Complete task lifecycle management system with state-based workflow. Define, refine, implement, and review tasks with automated quality gates and intelligent discovery.4---5
6# Purpose
7
8Manage complete task lifecycle from initial definition through implementation to review and completion. Provides state-based workflow with automated transitions, intelligent task discovery, quality gates, and framework-aware implementation patterns.
9
10**Tip**: For smoother workflow without permission prompts, consider adding `["Read", "Write", "Edit", "Glob", "Bash", "TodoWrite"]` to `dangerouslySkipPermissions` in your project's `.claude/settings.json`.
11
12## Variables
13
14TASK_ID_PREFIX: TASK # Project prefix for task IDs (TASK, BROOKLY, JIRA, etc.)
15TASK_ID_START: 1 # Starting number for new task sequences
16TASK_ID_PADDING: 3 # Number of digits for task IDs (3 = 001, 006, 042)
17TASK_DIR: ./tasks # Directory where task files are stored
18TASK_FILE_FORMAT: {prefix}-{id} [{state}] ({category}): {slug}.md # Filename template
19
20STATE_INITIAL: toRefine # First state after task creation
21STATE_READY: toImplement # Requirements refined, ready for coding
22STATE_REVIEW: toReview # Implementation complete, needs review
23STATE_COMPLETE: done # Fully finished and approved
24
25ENABLE_LINT: true # Run linting during implement/review workflows
26ENABLE_TYPECHECK: true # Run type checking validation
27ENABLE_BUILD: true # Run build verification
28ENABLE_TESTS: true # Run test suite execution
29ENABLE_SECURITY_SCAN: false # Run security vulnerability scanning
30
31AUTO_DETECT_FRAMEWORK: true # Automatically detect project framework
32DEFAULT_FRAMEWORK: generic # Fallback framework if detection fails
33SUPPORTED_FRAMEWORKS: generic, nextjs, django, react, python # Currently supported
34
35COMMIT_STYLE: conventional # Commit message convention (conventional, angular, custom)
36
37## Workflow
38
391. **Parse User Request**
40
41 - Identify workflow command intent from user input
42 - Commands: "define task", "refine task", "implement task", "review task"
43 - Extract task identifier if provided (ID, keywords, category)
44 - Example: "define task: add user authentication" → Intent: define, Description: "add user authentication"
45
462. **Determine Workflow Phase**
47
48 - IF: "define" OR "create" OR "new task" → Route to Define workflow
49 - IF: "refine" OR "clarify" OR "interview" → Route to Refine workflow
50 - IF: "implement" OR "code" OR "build" → Route to Implement workflow
51 - IF: "review" OR "check" OR "validate" → Route to Review workflow
52 - Example: "refine task 006" → Phase: refine, Task ID: 006
53
543. **Detect Project Framework**
55
56 - IF: AUTO_DETECT_FRAMEWORK is true → Scan for framework indicators
57 - Check for: package.json (Node.js), requirements.txt (Python), go.mod (Go)
58 - Analyze dependencies and config files to determine specific framework
59 - Example: package.json with "next" dependency → Framework: nextjs
60
614. **Route to Cookbook**
62
63 - Based on workflow phase and detected framework
64 - Define workflow: cookbook/define.md (framework-agnostic)
65 - Refine workflow: cookbook/refine.md (framework-agnostic)
66 - Implement workflow: cookbook/implement/{framework}.md (e.g., generic.md, nextjs.md)
67 - Review workflow: cookbook/review/{framework}.md (e.g., generic.md, nextjs.md)
68 - Example: Phase=implement + Framework=nextjs → cookbook/implement/nextjs.md
69
705. **Execute Workflow**
71
72 - Load appropriate cookbook workflow
73 - Follow workflow steps with current Variables configuration
74 - Use TASK_DIR, TASK_ID_PREFIX, and other Variables throughout
75 - Apply quality gates if ENABLE_* variables are true
76 - Example: Execute implement workflow using TASK-006, run lint+typecheck+build+test
77
786. **Report Results**
79
80 - Summarize workflow execution
81 - Show task state transitions (if applicable)
82 - List files created/modified
83 - Display next steps in workflow
84 - Example: "Task TASK-006 transitioned from [toImplement] to [toReview]. Run review workflow next."
85
86## Cookbook
87
88### Define Task Workflow
89
90- IF: User wants to create new task specification
91- THEN: Read and execute: `.claude/skills/task-workflow/cookbook/define.md`
92- EXAMPLES:
93 - "define task: add user authentication"
94 - "create new task for fixing navigation bug"
95 - "new task: implement dark mode"
96
97### Refine Task Workflow
98
99- IF: User wants to clarify task requirements
100- THEN: Read and execute: `.claude/skills/task-workflow/cookbook/refine.md`
101- EXAMPLES:
102 - "refine task 006"
103 - "clarify requirements for TASK-006"
104 - "interview me about the authentication task"
105
106### Implement Task Workflow
107
108- IF: User wants to implement task
109- THEN: Detect framework, Read and execute: `.claude/skills/task-workflow/cookbook/implement/{framework}.md`
110- Framework detection: generic (default), nextjs, django, react, python
111- EXAMPLES:
112 - "implement task 006" → cookbook/implement/generic.md (default)
113 - "implement task 006" (in Next.js project) → cookbook/implement/nextjs.md
114 - "build TASK-006" → framework-aware routing
115
116### Review Task Workflow
117
118- IF: User wants to review task
119- THEN: Detect framework, Read and execute: `.claude/skills/task-workflow/cookbook/review/{framework}.md`
120- Framework detection: generic (default), nextjs, django, react, python
121- EXAMPLES:
122 - "review task 006" → cookbook/review/generic.md (default)
123 - "review task 006" (in Next.js project) → cookbook/review/nextjs.md
124 - "validate TASK-006" → framework-aware routing