Workflow Execute

Workflow — Execute

Step 3 of the Persimmon workflow. Implement the plan one task at a time.

Prerequisites

An approved plan exists in docs/plans/. If not, go to workflow-plan.

Process

1. Work tasks in order. For each ready task:
   • Implement only what the task scopes — YAGNI. Don't pull future tasks forward.
   • Follow the relevant domain mother's child skill for patterns (stack-*, ai-*, data-*, etc.).
   • Run the task's verification (the EARS criteria) before marking it done — see workflow-verify.
2. Park human-blocked tasks. Note what's needed from the client; continue with unblocked tasks. Never fabricate a client decision to unblock yourself.
3. Keep the plan updated. Check off tasks; record any scope change back into the spec (and re-confirm if Business meaning shifts).
4. Commit per task with a business-framed message: what changed for the operator first, technical detail second.

Background agents on an auto-deploy Railway repo

When fanning out background coding agents on a client repo that auto-deploys on push (most Persimmon projects), four rules keep parallelism from corrupting main:

1. Partition by disjoint files. Map ownership first (which component/action/route each task touches); never let two concurrent agents edit the same file. Most components and Server Actions are disjoint — route tasks accordingly.
2. Serialize the shared chokepoints. Shared CSS/tokens and global layout files are where parallel agents collide. Tell each agent not to edit them but to report the styles it needs; apply those centrally. Page-scoped components an agent may own outright.
3. One deploy gate, through you. Push auto-deploys on Railway, so commit→push→deploy→staging-verify stays serialized in the orchestrator. Commit only complete, disjoint agent output — never let a half-built agent's files ride along on a push.
4. A standing brief, not re-explanation. Point every agent at CLAUDE.md + .claude/project-rules.md + a short docs/AGENT-BRIEF.md (stack, canonical patterns, no-dup rule, deploy/verify flow) so you ground them once, not per dispatch.

Commit message convention

{operator-facing summary}

{technical detail}

Plan: docs/plans/YYYY-MM-DD-{topic}.md (Task N)

Parallelism (opt-in)

For genuinely independent tasks, you may dispatch parallel subagents — but only when tasks don't share files and each has clear, self-contained acceptance criteria. Default to sequential.

When NOT to use

If there's no plan, or the work is trivial, this skill doesn't apply.

Relationship to other skills

Preceded by workflow-plan; each task gated by workflow-verify; failures handed to workflow-debug; finished via workflow-code-review → workflow-finish.