Agent Common

Agent Common (Shared Preamble)

Preloaded into every agent except plan-gap-reviewer (it loads no skills and reads no memory, by design). Read-only agents and write agents share it; where your agent doc is narrower or names a role-specific write, your agent doc wins.

Memory First (CRITICAL — DO NOT SKIP)

Read memory before any work:

Bash(command="mkdir -p .cc10x/")
Read(file_path=".cc10x/activeContext.md")
Read(file_path=".cc10x/patterns.md")
Read(file_path=".cc10x/progress.md")

Memory contains prior decisions, known gotchas, and current context. Without it, you work blind.

Run the mkdir -p .cc10x/ step unless your agent doc is read-only; the router creates .cc10x/ and .cc10x/qa/<workflow>/ for you, so the step is a no-op safety net. Keep the trailing slash: the QA isolation guard's allowlist is the prefix .cc10x/, and it denies the bare form mkdir -p .cc10x in QA plan phases.

Narrower agent protocols win: if your agent doc deliberately narrows this protocol (anti-anchoring reviewers such as code-reviewer skip activeContext.md; plan-gap-reviewer reads no memory at all; qa-researcher creates no files and runs no mkdir), follow the agent doc — the narrowing is intentional, not an omission.

Memory ownership: Do NOT edit the memory files (.cc10x/activeContext.md, .cc10x/patterns.md, .cc10x/progress.md) directly. Output your Memory Notes (see Memory Notes Format). The router persists memory at workflow-final via task-enforced workflow. Every other .cc10x/ path you write only where your agent doc names it (the QA agents write under .cc10x/qa/); .cc10x/workflows/* is router-owned. Sole carve-out: bug-investigator MAY append [DEBUG-N] investigation lines to .cc10x/activeContext.md under ## Debug History ONLY — no other agent, file, or section.

Key anchors:

• activeContext.md: ## Learnings, ## Recent Changes
• patterns.md: ## Common Gotchas
• progress.md: ## Verification

Domain Glossary (read-only)

Read CONTEXT.md at the repo root if present. Use the project's domain vocabulary in all output — test names, variable names, findings, contracts. Respect any ADRs in docs/adr/ for the area you're touching.

Do NOT write or edit CONTEXT.md from this skill. agent-common is loaded by every agent except plan-gap-reviewer, including the read-only ones that must never mutate repository artifacts. CONTEXT.md is written inline only by designated shaping phases (planner, exploration DESIGN mode, doc-syncer) via the cc10x:domain-modeling skill; builders and investigators read it and obey. If you discover a glossary contradiction, emit a **Domain proposal:** line in Memory Notes — do not resolve it.

SKILL_HINTS

If your prompt includes SKILL_HINTS, invoke each skill via Skill(skill="{name}") after memory load. Also: after reading patterns.md, if ## Project SKILL_HINTS section exists, invoke each listed skill. If a skill fails to load, note it in Memory Notes and continue.

Frontmatter skills: preloads are your role-core skills and are already loaded; SKILL_HINTS carries situational skills, and the router is the only authority that adds situational skills. Do not self-activate internal cc10x skills not passed in SKILL_HINTS — deterministic hints keep dispatches reproducible. The one agent-owned invocation: the planner may invoke cc10x:plan-review-gate itself, as its agent doc prescribes.

CONTRACT Envelope

Every agent's final response uses ONE canonical shape:

1. Line 1: CONTRACT {json} — the fast-path signal (s=STATUS, b=BLOCKING, cr=CRITICAL_ISSUES).
2. Line 2: ## Heading — fallback verdict signal.
3. Then a fenced ```yaml Router Contract block carrying your agent's required structured fields (STATUS must appear there too, not just the envelope).
4. Then the prose sections your agent doc prescribes.

The STATUS in the fenced YAML block decides; the envelope and heading are the fast path, and the fallback only when the YAML block is absent. If they disagree, the YAML decides. The final contract response is your LAST message — never call a tool (including TaskUpdate) after emitting it: the router parses only your last message, and a trailing tool result would become it. If a SubagentHandback tool is available, pass the whole contract as its message and make that call your last action. No agent holds the TaskUpdate tool or owns task completion: the router completes every task after it validates your contract, so you never call TaskUpdate.