Back to Plate

{{TITLE}}

docs/plans/templates/task.md

53.0.610.9 KB
Original Source

{{TITLE}}

Objective: TODO: Write the exact active task objective after creating this file.

Goal plan: {{PLAN_PATH}}

Template: {{TEMPLATE_PATH}}

Task source:

  • type: pending
  • id / link: pending
  • title: pending
  • acceptance criteria: pending

Completion threshold:

  • TODO: Define the exact task done state.
  • Task closure is legal only when the source-of-truth acceptance criteria are satisfied or explicitly narrowed, required verification evidence is recorded, code-review and release-artifact gates are closed when applicable, tracker/PR sync is complete or marked N/A with reason, and node .agents/rules/autogoal/scripts/check-complete.mjs {{PLAN_PATH}} passes.

Verification surface:

  • TODO: Name the tests, typecheck, lint, browser proof, source audit, PR/tracker sync, or other artifact proving the threshold.

Constraints:

  • Preserve existing user-facing behavior outside the task scope.
  • Prefer the durable ownership boundary over caller-by-caller patches.
  • Do not create PRs, comments, commits, or pushes unless the task/user/skill requires them.
  • Do not add broad ceremony when the task is trivial or docs-only.

Boundaries:

  • Source of truth: TODO.
  • Allowed edit scope: TODO.
  • Browser surface: TODO.
  • Tracker sync: TODO.
  • Non-goals: TODO.

Blocked condition:

  • TODO: Name the missing source context, transcript, repro, access, command, or user decision that stops autonomous work.

Task state:

  • task_type: pending
  • task_complexity: pending
  • current_phase: intake
  • current_phase_status: in_progress
  • next_phase: implementation
  • goal_status: active

Current verdict:

  • verdict: pending
  • confidence: pending
  • next owner: task
  • reason: pending

Completion rule:

  • Do not call update_goal(status: complete) while any required checklist item remains unchecked. If an item does not apply, check it and add N/A: <reason>.
  • Do not call update_goal(status: complete) until every completion threshold above is satisfied, final handoff evidence is recorded, and node .agents/rules/autogoal/scripts/check-complete.mjs {{PLAN_PATH}} passes.
  • Do not create hook state for this goal. This file plus the active goal are the durable state.

Start Gates:

GateAppliesEvidence
Skill analysis before editspendingpending
Active goal checked or createdpendingpending
Source of truth read before editspendingpending
Tracker comments and attachments readpendingpending
Video transcript evidence requiredpendingpending
docs/solutions checked for non-trivial existing-code workpendingpending
TDD decision before behavior change or bug fixpendingpending
Branch decision for code-changing taskpendingpending
Release artifact decisionpendingpending
Browser tool decision for browser surfacependingpending
PR expectation decisionpendingpending
Tracker sync expectation decisionpendingpending

Work Checklist:

  • Objective includes outcome, completion threshold, verification surface, constraints, boundaries, and blocked condition.
  • Task source classified with source type, id/link, title, task type, acceptance criteria, caveats, likely files/routes/packages, browser surface, and root-cause layer.
  • Required video or screen-recording evidence is cached/read as normalized <video-transcripts> XML, or marked N/A with reason.
  • Nearby repo instructions and implementation patterns read before edits.
  • Implementation fixes the right ownership boundary, or the narrower choice is recorded with reason.
  • Release artifact requirement recorded: changeset, registry changelog, or N/A with reason.
  • Final handoff shape decided: bug/feature/testing/batch/review/tracker requirements, PR body sync, and issue/Linear sync when applicable.
  • Branch handling recorded for code-changing work: dedicated branch used, new branch needed, or N/A with reason.
  • Local-env-rot retry policy recorded for any surprising repo-wide failure: reinstall/rerun evidence or N/A with reason.
  • Workspace authority recorded: every proof command names the cwd/tool that owns the changed behavior.
  • High-risk note recorded for public API, runtime, package-boundary, browser behavior, agent-action, or command-contract changes, or marked N/A with reason.
  • Review/autoreview target selected from actual diff state for non-trivial implementation work, or marked N/A with reason.
  • Agent-native review decision recorded for .agents/**, .claude/**, .codex/**, skills, hooks, commands, prompts, or user-action tooling.

Completion Gates:

GateAppliesRequired actionEvidence
Named verification thresholdpendingRun the command, proof, source audit, or artifact check named in this planpending
Bug reproduced before fixpendingRecord failing test/repro or N/A with reasonpending
Targeted behavior verificationpendingRun focused test/proof for changed behavior or record N/Apending
TypeScript or typed config changedpendingRun relevant typecheckpending
Package exports or file layout changedpendingRun pnpm brl before final verification and keep generated barrel updatespending
Package manifests, lockfile, or install graph changedpendingRun pnpm install and relevant package checkspending
Agent rules or skills changedpendingRun pnpm install and verify generated skill syncpending
Workspace authority proofpendingRun verification in the owning repo/package/app/route/tool and record cwd; do not count the wrong workspace as proofpending
Browser surface changedpendingCapture Browser Use proof or record explicit waiver/blockerpending
Browser final proofpendingAttach screenshot or exact browser verification caveat when browser proof appliespending
CI-controlled template output changedpendingRestore generated template output or record why it is intentionally keptpending
Package behavior or public API changedpendingAdd a changeset or record why no changeset appliespending
Registry-only component work changedpendingUpdate docs/components/changelog.mdx or record N/Apending
Docs or content changedpendingFor docs-heavy work, use --template docs; for incidental docs, verify source-backed claims, links, examples, and rendered output or record N/Apending
High-risk mini gatependingFor public API/runtime/package-boundary/browser/agent-action/command-contract changes, record realistic failure mode, proof plan, and why the chosen boundary is right; otherwise N/Apending
Agent-native review for agent/tooling changespendingFor .agents/**, .claude/**, .codex/**, skills, hooks, commands, prompts, or user-action tooling, load .agents/skills/agent-native-reviewer/SKILL.md and close accepted/actionable findings, or record N/Apending
Local install corruption suspectedpendingRun pnpm run reinstall once, rerun the exact failing command, or record N/Apending
Autoreview for non-trivial implementation changespendingLoad .agents/skills/autoreview/SKILL.md; use dirty local --mode local, branch/PR --mode branch --base <base>, or committed slice --mode commit --commit <ref> until no accepted/actionable findings, or record N/A for docs-only/trivial/no local patchpending
PR create or updatependingRun check before PR work and sync PR body to the task-style final handoffpending
Task-style PR body verifiedpendingVerify the PR body with gh pr view --json body; it must preserve auto-release blocks when applicable, must not include a current-PR self-link, and must include an issue/tracker/fix line when applicable, confidence, Reproduced/Verified table, Outcome, Caveat, Design, and Verified sections as applicablepending
PR proof image hostingpendingIf PR body needs browser proof, replace local image paths with hosted GitHub URLs or record N/Apending
Tracker sync-backpendingPost concise issue/Linear sync after PR exists, or record N/A/blockerpending
Final handoff contractpendingFill the final handoff fields below with exact PR/issue/confidence/tests/browser/outcome/caveats/design/verification content or N/A reasonpending
Final lintpendingRun pnpm lint:fix or scoped equivalentpending
Goal plan completeyesRun node .agents/rules/autogoal/scripts/check-complete.mjs {{PLAN_PATH}}pending

Phase / pass table:

PhaseStatusEvidenceNext
Intake and source readin_progresscreated planimplementation
Implementationpendingverification
Verificationpendingcloseout
PR / tracker syncpendingfinal response
Closeoutpendingfinal response

Findings:

  • None yet.

Decisions and tradeoffs:

  • None yet.

Implementation notes:

  • None yet.

Review fixes:

  • None yet.

Error attempts:

Error / failed attemptCountNext different moveResolution
None yet0

Verification evidence:

  • Pending.

Final handoff contract:

  • PR line: pending
  • Issue / tracker line: pending
  • Confidence line: pending
  • Flow table:
    • Reproduced: tests pending, browser pending
    • Verified: tests pending, browser pending
  • Browser check: pending
  • Outcome: pending
  • Caveat: pending
  • Design:
    • Chosen boundary: pending
    • Why not quick patch: pending
    • Why not broader change: pending
  • Verified: pending
  • PR body verified: pending

Task-style PR body contract:

  • Preserve any existing <!-- auto-release:start --> block. If a changeset is part of the diff and repo policy expects auto release, include that block.
  • Use the final handoff fields in this order: issue, tracker, or fix line when applicable; confidence line; Reproduced / Verified table; Outcome; Caveat; Design; and Verified.
  • Never include a line that links to the current PR itself. The current PR URL belongs in the final response, not in its own description.
  • Do not replace this with a generic Summary / Verification PR body, an adaptive prose body from a git helper skill, or an unrelated generated badge footer unless the caller or repo template explicitly asks for it.
  • Proof is gh pr view --json body output or a concise source-backed summary of that output.

Final handoff / sync:

  • PR: pending
  • Issue / tracker: pending
  • Browser proof: pending
  • Caveats: pending

Timeline:

  • {{CREATED_AT}} Task goal plan created.

Reboot status:

QuestionAnswer
Where am I?Intake and source read
Where am I going?Implementation, verification, PR/tracker sync, closeout
What is the goal?TODO: Fill from Objective
What have I learned?See Findings
What have I done?See Timeline

Open risks:

  • Pending.