Every session runs through the l-01-session-job-lifecycle session job lifecycle: orient → ground → frame → decide →
build → close. The job type (bug / feature / triage / research) is a lens during framing, not a gate.
The only task-format decision is the l-01-session-job-lifecycle skill’s build-mode step.
Every build keeps these rules:
c-08-ar-coordination-context-resolver.l-01-session-job-lifecycle skill’s frame plan gate).system/tools.md when available.At decide, the l-01-session-job-lifecycle skill picks one of:
The job answers a question or assesses something and changes no code — no worktree, no task file, no closeout. Research and triage jobs usually exit here; they may recommend or spawn a build job.
A code change small enough to carry inline this session: worktree-backed, with no durable task file.
After approval, the build closes through the c-12-closeout worktree closeout, which commits code
first, refreshes onboarding metadata to that code commit, commits memory, then updates the ledger.
w-02-light-task-workflow)Use w-02-light-task-workflow when the work needs a durable task file but still fits a compact plan:
ar-coordination/tasks/<repo>/<task-slug>/task.md
The task file holds requirements, implementation steps, proposed examples, decisions, open questions, and references; the checklist is the live execution state. Use it for documentation restructures, medium refactors, multi-step cleanup, and work that might survive more than one session.
When the work outgrows a single-page plan — broad cross-repo or high-risk changes, or several distinct
slices that each need their own checklist and commit — escalate to a master + light sub-task series
(master-template.md): one wrapper folder with a master task.md plus flat, numbered sub-task files,
one shared worktree, a commit per slice, and a single release at the end. This composition replaces the
retired heavy workflow.
Every build is worktree-backed (only read-only exits skip the worktree). The c-09-git-worktree-manager skill creates the task
worktree; a worktree-backed task has a contract.md beside the task file. The c-09-git-worktree-manager skill owns the worktree
lifecycle, integration, and cleanup; c-12-closeout runs the closeout itself. A master series runs in
one shared worktree for the whole series.
Closeout and commit approval are separate from implementation approval. The agent presents a dry-run
preview before any c-12-closeout closeout creates commits. The git-landing flow (direct vs PR-gated) is
deferred to the repo’s system/git-workflow.md when present.
| Situation | Build mode |
|---|---|
| Answer or assessment, no code change | Read-only exit |
| One-session code change, low risk | Chat build (worktree, no task file) |
| Needs a durable plan or checklist | w-02-light-task-workflow light task |
| Outgrows a single-page plan, or broad/high-risk | Master + light sub-task series |
| Parallel implementation or explicit closeout tracking | Any build mode — all builds are worktree-backed via the c-09-git-worktree-manager skill |