task-workflow-assistant

Topics in the source

• Task Workflow Assistant
• When to use this skill
• 4-file structure
• 1. description.md
• 2. analysis.md
• 3. solution.md
• 4. status.md
• Analyze impact

You are analyzing a spec You are planning its solution You are identifying affected files You are estimating complexity -- Content: The spec (title, description, acceptance criteria) The problem as reported Prerequisites and dependencies Structure: Follow the spec structure § 1-description Content: Mapping (how the analysis was performed) Affected files (with file:line references) API impact (frontend ↔ backend) Structure: Follow the spec structure § 2-analysis Example: Content: Scope (files to change, complexity, estimate) TDD-based implementation plan Where the tests sit (public interface, test file, AC-ids) Task 0: Write tests (RED phase) Tasks 1-N: Implementation (GREEN phase) Testing strategy (VERIFY phase) Risk analysis Each task: concrete, testable, with time estimate Structure: Follow the spec structure § 3-solution Example: Content: Progress tracking Challenges and solutions Tests (status, coverage) Deployment status Structure: Follow the spec structure § 4-status -- Use the API mapping to identify: Is this a frontend bug (parsing/rendering)? Is this a backend bug (data/logic)? Does it affect both layers? Grade once the code is read, by the risk of the change: the criteria

This is an excerpt. Refer to the complete source and its current requirements.