implement-quick-test

Executes one fully specified implementation brief with bounded paths, proof commands, and escalation rules.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill implement-quick-test-skyrocoster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-quick-test
Source: https://github.com/skyrocoster/dnd-kids-resources/tree/main/.opencode/skills/implement-quick-test
Command: npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill implement-quick-test-skyrocoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents scope creep and uncontrolled edits during delegated implementation by forcing the executor to work only from a fully settled brief with exact authorized paths, verified facts, and a fixed proof contract. ## Core Features & Use Cases - Brief validation: Blocks execution before reading source if the brief is missing GOAL, AUTHORIZED PATHS, KNOWN FACTS, CHANGE, PROOF CONTRACT, or ESCALATE IF fields. - Bounded execution: Reads only authorized paths, makes the smallest single atomic change, and runs only the exact focused commands named in the proof contract. - Structured reporting: Returns a fixed RESULT/EDITS/REGRESSION/CHECKS/SCOPE AUDIT report with escalation instead of improvisation when facts are wrong or scope grows. - Use Case: A coordinator agent decomposes a plan into small stages and hands one settled stage to this executor, which implements exactly that change, proves it with the named commands, and stops. ## Quick Start Ask the agent to implement this quick brief, providing the GOAL, AUTHORIZED PATHS, KNOWN FACTS, CHANGE, PROOF CONTRACT, and ESCALATE IF fields for one atomic change.

Frequently Asked Questions about implement-quick-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate a small code change to an AI executor safely?▼

Provide a complete brief with GOAL, AUTHORIZED PATHS, KNOWN FACTS, a single atomic CHANGE, a PROOF CONTRACT with exact commands, and ESCALATE IF boundaries. The executor reads only those paths, makes the minimal edit, runs the named commands, and stops after the first green proof.

What happens if the implementation brief is incomplete?▼

Execution is blocked before any source is read if a required field is missing, a path is a broad conditional glob, the change bundles multiple outcomes, or the proof delegates a decision. This prevents the executor from improvising on underspecified work.

Can the executor fix failing tests on its own?▼

It may make at most one distinct in-scope repair and rerun verification once. Two failed verification runs result in FAILED status, and it never weakens the proof contract or expands scope to force a pass.

When does the executor escalate instead of completing the change?▼

It escalates when a known fact is wrong, another path is needed, scope grows, or a design, architecture, API, data, migration, or contract decision appears. It leaves truthful partial work in place and reports the exact blocker.

Does the executor run full test suites or commits after finishing?▼

No. It skips closeout, documentation regeneration, full suites, browser validation, and commits unless the brief explicitly names a focused command. Post-implementation routing belongs to the coordinator.