Skip to content
Agentic Coding Toolkit

Work

Execute an implementation plan systematically — phase by phase, with TDD discipline where applicable, continuous verification, and automatic commits.

Usage

Section titled “Usage”
Terminal window
/act:workflow:work <plan-file> [type]

Arguments:

  • plan-file (required): path to the plan file
  • type (optional, default: lite):
    • official — load official Flutter rules only
    • lite — load essential patterns, principles, and breaking changes
    • full — load all knowledge including setup guides

Examples

Section titled “Examples”
Terminal window
/act:workflow:work ai_specs/feature-plan.md
/act:workflow:work ai_specs/feature-plan.md full
/act:workflow:work ai_specs/feature-plan.md official

What it does

Section titled “What it does”

1. Reads the plan and spec

Section titled “1. Reads the plan and spec”

Loads the plan file and any referenced spec for full requirements context.

2. Commits the plan

Section titled “2. Commits the plan”

If the plan has uncommitted changes, commits it before starting work.

3. Sets up the project

Section titled “3. Sets up the project”

If no pubspec.yaml exists, creates a new Flutter or Dart project based on the plan’s content using /flutter-create or /dart-create.

4. Loads Flutter knowledge

Section titled “4. Loads Flutter knowledge”

Primes the AI with patterns, principles, and breaking changes based on the type parameter. Also loads TDD and robot testing guidance if the plan requires them.

5. Executes each phase

Section titled “5. Executes each phase”

For each phase in the plan:

  • Reads referenced files and looks for similar patterns in the codebase
  • Implements with TDD discipline — for TDD: tasks, follows strict RED → GREEN → REFACTOR cycles (one test at a time)
  • Commits frequently — small, conventional commits at logical checkpoints
  • Tests continuously — flutter analyze and flutter test after each phase
  • Updates progress — marks tasks - [x] in the plan file as they’re completed

6. Ships it

Section titled “6. Ships it”

After all phases complete:

  • Runs full test suite and analysis
  • Creates a pull request with summary and testing notes

Key principles

Section titled “Key principles”

Start with a thin end-to-end slice

Section titled “Start with a thin end-to-end slice”

Phase 1 proves the critical path across all layers. Never build entire layers in isolation (all models, then all services, then all UI).

Test-first with vertical slices

Section titled “Test-first with vertical slices”

For TDD: tasks: write one failing test → minimal implementation → refactor → repeat. Never batch tests.

Commit early and often

Section titled “Commit early and often”

Every commit must be in a working state — no compile errors, no analysis failures, all tests passing.

Ship complete features

Section titled “Ship complete features”

All tasks marked - [x] before creating the PR. A finished feature that ships beats a perfect feature that doesn’t.

Error handling

Section titled “Error handling”
  • Compilation errors — fixed immediately before proceeding
  • Test failures — investigated and fixed at the root cause
  • Unexpected complexity — subtasks broken down further, user informed
  • Blocked progress — documented in the plan, user asked for clarification
Section titled “Related commands”