🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Task Development Workflow
πŸ¦€ ClawHub

Task Development Workflow

by @anikgnr

TDD-first development workflow with structured planning, task tracking, and PR-based code review. Use when building software projects that require clarificat...

Versionv1.0.0
Downloads3,231
#clawhub
TERMINAL
clawhub install task-development-workflow

πŸ“– About This Skill

name: task-development-workflow description: TDD-first development workflow with structured planning, task tracking, and PR-based code review. Use when building software projects that require clarification phases, planning approval gates, Trello task management, test-driven development, Git branching policies, and PR feedback loops with reviewers.

Task Workflow

A structured development workflow enforcing quality through planning, TDD, and code review.

Workflow Overview

Clarify β†’ Plan β†’ Approve β†’ Implement (TDD) β†’ PR β†’ Review β†’ Merge β†’ Next Task

Phase 1: Clarification

Before any implementation, ask questions to clarify:

  • Business requirements and goals
  • UI/UX flow expectations
  • Architecture decisions
  • Technical constraints
  • Ambiguous requirements

    • Do not proceed until requirements are clear.

    Phase 2: Planning & Approval

    1. Present a detailed plan with task breakdown 2. Keep tasks small and focused 3. Wait for explicit approval before starting 4. No implementation without approval

    Phase 3: Task Tracking Setup

    Set up Trello board (or similar) with columns:

  • πŸ“ Backlog
  • πŸ“‹ To Do
  • πŸ”¨ In Progress
  • πŸ” Review
  • βœ… Done

    • All tasks must be tracked on the board.

    Phase 4: Implementation (Per Task)

    For each task:

    1. Move card to "In Progress" 2. Write tests first (TDD): - Define expected behavior in tests - Run tests (should fail) - Implement the feature - Run tests (should pass) 3. Commit after task completion 4. Tests may be skipped only with explicit approval

    Phase 5: Branching & PR Policy

    Rules:

  • Never push directly to main
  • Never change the default branch β€” main must always remain default
  • Create feature branches for each task

    • After task completion: 1. Open PR from task branch β†’ main 2. Include Trello task link in PR description 3. Move card to "Review" 4. Notify Reviewer with both Trello link and PR link

    Phase 6: PR Feedback Loop

    When CR comments arrive: 1. Move task back to "In Progress" 2. Address all review comments 3. Push fixes 4. Notify Reviewer to re-review (include both links)

    Repeat until approved.

    Phase 7: Merge Gate

  • Only pick the next task after current PR is merged
  • Move completed card to "Done"
  • Then proceed to next task from "To Do"

    • Flow Diagram

    Backlog β†’ To Do β†’ In Progress β†’ Review β†’ Done
                      ↑            β”‚
                      └─── CR β”€β”€β”€β”€β”€β”˜

    New Project Bootstrap

    For new projects: 1. Create repository with initial README 2. Push to remote 3. Then begin implementation tasks

    Key Principles

  • Quality over speed β€” TDD catches bugs early
  • Small tasks β€” easier to review and merge
  • Clear communication β€” always notify reviewers
  • No shortcuts β€” follow the process every time