spec-execution-fastpath

Estrellas12

Forks1

Actualizado3 de junio de 2026 a las 09:10

Use when requirements or spec are clear and the implementation should be a minimal, repo-pattern-compatible diff. DO NOT USE FOR: unclear direction, broad redesign, or tasks without enough file/context evidence.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

funky-eyes

funky-eyes/best-copilot

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	spec-execution-fastpath
description	Use when requirements or spec are clear and the implementation should be a minimal, repo-pattern-compatible diff. DO NOT USE FOR: unclear direction, broad redesign, or tasks without enough file/context evidence.

Spec Execution Fastpath

Steps

Read only the user-provided paths, relevant spec, direct owner files, and immediate call chain.
Freeze scope: goal, files, constraints, non-goals, acceptance checks, verification budget.
Reuse existing patterns before adding abstractions.
Implement the smallest diff that satisfies the requirement.
Simplify recently touched code when it preserves behavior: reduce unnecessary nesting, remove redundant branches, improve names, and align with local style.
Add or update focused tests when behavior changes.
Verify with the smallest sufficient command or static evidence.
For persistent task/spec work, update tasks.md status and memories/repo/current-workstreams.md before reporting completion.

Guardrails

Do not expand file ownership without returning to PM.
Do not add “future-proof” abstractions without present complexity.
Do not simplify by changing behavior, public contracts, error semantics, or observability.
Public contracts, auth, data, dependencies, CI, and runtime config require blast radius assessment.
Customization files require frontmatter/schema and residual-reference checks.
Chat-only progress is invalid for persistent MEDIUM/LARGE work.

Output

Return changed files, behavior summary, verification evidence, state-sync evidence when applicable, and residual risk.

Más de este repositorio

mismo repositorio

core-workflow-contract

funky-eyes/best-copilot

Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.

2026-07-1512

repo-init-manual-fallback

funky-eyes/best-copilot

Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.

2026-07-1512

senior-project-expert-workflow

funky-eyes/best-copilot

Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.

2026-07-1512

specification-writer-workflow

funky-eyes/best-copilot

Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.

2026-07-1512

subagent-driven-development

funky-eyes/best-copilot

Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.

2026-07-1512

target-spec-bootstrap

funky-eyes/best-copilot

Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.

2026-07-1512

name	spec-execution-fastpath
description	Use when requirements or spec are clear and the implementation should be a minimal, repo-pattern-compatible diff. DO NOT USE FOR: unclear direction, broad redesign, or tasks without enough file/context evidence.

Spec Execution Fastpath

Steps

Read only the user-provided paths, relevant spec, direct owner files, and immediate call chain.
Freeze scope: goal, files, constraints, non-goals, acceptance checks, verification budget.
Reuse existing patterns before adding abstractions.
Implement the smallest diff that satisfies the requirement.
Simplify recently touched code when it preserves behavior: reduce unnecessary nesting, remove redundant branches, improve names, and align with local style.
Add or update focused tests when behavior changes.
Verify with the smallest sufficient command or static evidence.
For persistent task/spec work, update tasks.md status and memories/repo/current-workstreams.md before reporting completion.

Guardrails

Do not expand file ownership without returning to PM.
Do not add “future-proof” abstractions without present complexity.
Do not simplify by changing behavior, public contracts, error semantics, or observability.
Public contracts, auth, data, dependencies, CI, and runtime config require blast radius assessment.
Customization files require frontmatter/schema and residual-reference checks.
Chat-only progress is invalid for persistent MEDIUM/LARGE work.

Output

Return changed files, behavior summary, verification evidence, state-sync evidence when applicable, and residual risk.