一键导入
task-workflow-manager
Complete task lifecycle management system with state-based workflow. Define, refine, implement, and review tasks with automated quality gates and intelligent discovery.
Complete task lifecycle management system with state-based workflow. Define, refine, implement, and review tasks with automated quality gates and intelligent discovery.
Headless browser automation using Playwright CLI. Use for browser testing, screenshots, scraping, and parallel browser sessions. Token-efficient CLI — no MCP overhead.
Analyzes project structure, dependencies, and patterns to generate comprehensive context documentation. Uses parallel agent execution for faster analysis. Helps understand unfamiliar codebases quickly.
Comprehensive code quality verification workflow that checks linting, formatting, type safety, tests, and build before committing code. Uses parallel agent execution for maximum speed. Non-destructive - only reports issues without making changes.
Auto-activating documentation cache with fresh API docs. Fetches and automatically consults cached documentation when user works with libraries/frameworks.
Fork a terminal session to a new terminal window. Use this when the user requests 'fork terminal' or 'create a new terminal' or 'new terminal: <command>' or 'fork session: <command>'.
| name | Task Workflow Manager |
| description | Complete task lifecycle management system with state-based workflow. Define, refine, implement, and review tasks with automated quality gates and intelligent discovery. |
| trigger | manual |
| allowed-tools | ["Read","Write","Edit","Glob","Bash","TodoWrite"] |
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.
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)
Parse User Request
Determine Workflow Phase
Detect Project Framework
Route to Cookbook
Execute Workflow
Report Results
.claude/skills/task-workflow/cookbook/define.md.claude/skills/task-workflow/cookbook/refine.md.claude/skills/task-workflow/cookbook/implement/{framework}.md.claude/skills/task-workflow/cookbook/review/{framework}.md