Quick Recap

Make completion state obvious at the end of every response.

Plan first

For finished work that needs a quick visual summary, build a recap page:

aos-plan-canvas new recap <plan-dir>                     # scaffold the plan folder
aos-plan-canvas open <plan-dir> --mode bdb-plan-builder  # render and open in the browser
aos-plan-canvas await <plan-dir>/plan.mdx                # keep listening until the verdict

The approved plan is the artifact: this template has no components, so there is no agenttrail map. The full loop: the plan-canvas skill — a plain CLI, identical on every harness.

Status Block

Every response that completes a unit of work must end with:

🟢 Actual concise status sentence

Rules:

• Keep the status line under 100 characters.
• Use 🟢 when the requested work is finished.
• Use 🟡 when non-routine follow-up remains; name the pending item.
• Use 🔴 only when blocked on user input.
• Put the status line at the very end of the response.
• Do not add ---, spacer lines, or any content after the status line.

Activation

The convention applies only while this skill is loaded or the user asks for it. AOS does not inject a managed AGENTS.md / CLAUDE.md block for it.

Choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked.

Examples

Finished work:

🟢 Updated quick recap docs with output examples

Non-routine follow-up remains:

🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks

Blocked on user input:

🔴 Need the production API key to continue