coding-agent
Implementation/review workflow for approved plans. Route ACP-first, then CLI fallback. Use after explicit APPROVE.
What this skill does
# Coding-Agent Skill ## Entry Gate Only execute this skill after explicit approval in the current conversation context: - `APPROVE` Approval must correspond to the latest pending plan in-context. If no matching approved plan exists, stop and request: `Run /plan first, then reply APPROVE.` ## Execution Workflow 1. Verify toolchain before major workflows: - `command -v codex && codex --version` - `command -v timeout` - `command -v gh` - `command -v claude || test -x ~/.claude/local/claude` 2. Gather read-only context first (`rg`, `git status`, `git diff`, docs). 3. Execute the approved implementation plan. 4. Run relevant validation: - formatting/lint - typecheck - unit/integration/e2e tests as applicable 5. Report exact commands run, outcomes, and residual risk. ### Review Routing Contract (Hard Rule) - Plan artifact review must run via `scripts/plan-review` or `scripts/plan-review-live`. - PR/code review must run via `codex review --base ...` (or `safe-review.sh` wrapper). - Do not publish a manual review summary before running the review command/wrapper. ## ACP-First Routing For harness-style implementation/review requests, ACP routing is mode-specific: - Implementation uses ACP first (via `acpx`) with CLI fallback. - Review keeps review-native `codex review --base` first, then ACP fallback. - CLI fallback chain remains mandatory if ACP is unavailable. - Direct ACPX calls in coding-agent orchestration must use `scripts/acpx-direct`. - Do not emit raw `acpx ...` commands from prompts or wrappers. - Disable ACP-first per run with `CODING_AGENT_ACP_ENABLE=0`. - Override ACPX binary path with `CODING_AGENT_ACPX_CMD`. - Override ACP agent alias with `CODING_AGENT_ACP_AGENT` (default: `codex`). Known runtime limitation: - Issue #43 tracks upstream ACP spawned-run observability and relay profile alias behavior. - Use repo-side mitigation and fallback guidance in `references/acp-troubleshooting.md`. ## Verbosity Mode (Progress Updates) `CODING_AGENT_VERBOSE` controls execution progress verbosity. Default is off. - `off` (default): concise progress updates. - `on`: include structured progress updates with `Now`, `Why`, and `Next`. Accepted truthy values (case-insensitive): `1`, `true`, `on`, `yes`, `verbose`. Accepted falsy values: unset, `0`, `false`, `off`, `no`. When verbose mode is on: - Send kickoff execution status in `Now/Why/Next` format. - For long-running tasks, send periodic status updates. - Send a completion update with outcome and blockers (if any). Verbosity must not block execution. After explaining intent, proceed immediately unless waiting on a required user decision or an explicit approval gate. Status updates are not a wait state: if the next step is executable, run it in the same turn. ### Long-Run Hard-Fail Policy For wrapper/CLI runs expected to exceed 30 seconds: - Emit `RUN_EVENT start`. - Emit `RUN_EVENT heartbeat` every 20 seconds while running. - Emit `RUN_EVENT interrupted` immediately on signal/timeout/interruption. - Emit `RUN_EVENT failed` on non-interruption errors. - Emit `RUN_EVENT done` on success. ## Guardrails - No bypass-by-default. Do not use approval-bypass flags unless the user explicitly requests bypass. - Use feature branches for code changes. - Keep changes scoped to the approved plan. ## Reference Loading Open only the references needed for the current task: - `references/WORKFLOW.md` - `references/STANDARDS.md` - `references/tooling.md` - `references/codex-cli.md` - `references/claude-code.md` - `references/reviews.md`
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.