agent-execution-mode
Agent Execution Mode
Use this skill whenever the user expects real completion: implementation, bug repair, hardening, architecture, design alignment, review, documentation, specification, repository-aware spec-driven delivery, or production-grade delivery.
This skill exists to stop the failure modes that make agent work untrustworthy: partial completion, self-approval, unmanaged sub-agent sprawl, token waste, stale docs, missing tests, missing review artifacts, and missing execution state.
When to use
Activate this skill when the request involves any of the following:
- implementing or fixing behavior that should be complete when returned
- bug investigation or bug fixing where the current behavior must be understood before edits begin
- hardening an existing implementation after regressions, repeated failures, or correctness gaps
- documentation creation or repair that must reflect the real project state instead of guessed behavior
- specification or plan creation before implementation, especially when the work should be driven by existing repository specification, planning, or task artifacts
- spec-driven delivery where implementation must stay governed by an existing repository-native specification, planning, task, ticket, or equivalent artifact packet
- architecture or system design work that needs explicit decisions and durable documentation
- code review, PR review, or self-review that must produce a reliable artifact
- design-driven work where implementation must be checked against a specification or screenshot
More from mwillbanks/agent-skills
code-discipline
Prevent trivial helpers, wrapper layers, rename-only utilities, duplicate constants, and local reinvention. Enforce reuse of platform primitives, framework capabilities, shared utilities, and proven libraries. Use when adding or reviewing logic, constants, composition, or UI structure so the agent keeps code disciplined and avoids technical debt.
32repo-standards-enforcement
Use this skill to enforce repository-wide standards for toolchain compliance, package-manager purity, type safety, testing, maintainability, and architecture. When a more specific skill exists for a concern such as final linting or formatting remediation, that more specific skill takes precedence over this skill's generalized guidance.
26biome-enforcement
Use this skill when a task touches code, tests, Biome config, or generated artifacts and Biome must remain the final remediation and enforcement pass using the required JSON changed-files command.
24execution-alignment-gate
Detects materially ambiguous or under-specified requests, selects the right clarification target, and enforces bounded alignment before execution, including spec-governed continuations and approval-gated manager handoffs. Use when ambiguity could cause wrong deliverables, wrong scope, wrong implementation path, avoidable rework, or token waste from repeated follow-up.
19speckit-feature-orchestrator
Orchestrates a full Speckit feature workflow from constitution amendment through specification, clarification, plan, tasks, and analysis as a chief-architect governor using subagents. Use when the repository already uses Speckit or the user explicitly asks for Speckit and wants to discuss, refine, or directly drive a new feature into implementation-ready Speckit artifacts in one controlled pass.
12review-remediation-gate
Close review findings deterministically, remediate blocking issues, and prove review closure. Use when the user says to fix review comments, address review findings, run a review-remediation pass, close out blockers, or finish work only after review issues are resolved.
7