tasks
Break into vertical slices, user stories, concrete tasks in MacroFlow.
When & Why to Use This Skill
The Tasks skill is designed to bridge the gap between high-level planning and technical execution by automating the decomposition of implementation plans into actionable items. It specializes in breaking down complex architectures into vertical slices, user stories, and concrete tasks, enabling teams to prioritize workflows and maintain a structured sprint backlog within the MacroFlow framework.
Use Cases
- Agile Sprint Planning: Automatically transform a broad implementation plan into detailed user stories and a prioritized sprint backlog for development teams.
- Technical Task Decomposition: Break down complex software architecture decisions into granular, concrete tasks to facilitate easier assignment and progress tracking.
- Incremental Feature Development: Define 'vertical slices' of a project to ensure that development efforts result in functional, testable increments of the product.
- Workflow Optimization: Use structured task graphs to identify dependencies and optimize the sequence of operations from planning to the implementation phase.
| name | tasks |
|---|---|
| description | Break into vertical slices, user stories, concrete tasks in MacroFlow. |
Tasks Skill
Overview
The Tasks phase breaks down the plan into vertical slices, user stories, and concrete tasks.
Purpose
- Decompose plan into actionable items
- Create user stories and tasks
- Prioritize work
- Track progress
Inputs
- Implementation plan
- Architecture decisions
Process
- Break down into vertical slices
- Define user stories
- Create concrete tasks
- Assign priorities and estimates
Outputs
- Task breakdown
- User stories
- Sprint backlog
Grok Integration
Use Grok for task decomposition and prioritization. Temperature: 0.3 for structured output.
Next Phase
Proceed to Implement when tasks are defined.
Instructions
- Create task graph.
- Vertical slices.
Examples
- Input: Plan.
- Output: Concrete tasks.
Learned Patterns
- User stories.