Execute a single spec step and return SUCCESS, FAILED, or GAP results.
npx skills add https://github.com/wilddeer/specops --skill spec-step-execution
Please help me install this Agent Skill. Skill: spec-step-execution Source: https://github.com/wilddeer/specops/tree/main/skills/spec-step-execution Command: npx skills add https://github.com/wilddeer/specops --skill spec-step-execution
Executing a single step from a spec can be prone to ambiguity, misinterpretation, and inconsistent results across sessions; this Skill enforces a zero-ambiguity workflow for step execution.
Provide the spec file path, the step number or name, and any existing progress or research context to execute a single step from the spec.
High-intent search queries and answers about installing and using this skill.
Deterministic spec step execution requires providing the exact step name or number and any existing research context, ensuring strict step-by-step execution with explicit inputs and zero ambiguity. It outputs structured SUCCESS, FAILED, or GAP results with verification status.
Gap detection in spec step execution identifies scenarios not covered by the spec, returning a GAP result with clear context and guidance. This structured reporting mechanism highlights missing specifications to prevent ambiguous execution paths.
Spec execution provides structured results by returning SUCCESS, FAILED, or GAP statuses. Each result includes a clear summary, explicit verification status, and optional observations, ensuring strict deterministic step-by-step execution with zero ambiguity.
To start executing a spec step, you need to provide the spec file path, the specific step number or name, and any existing progress or research context. This ensures deterministic single-step execution with explicit inputs and structured outcome reporting.
Deterministic step-by-step spec execution should be applied to scenarios requiring strict execution and explicit verification. It is necessary when consistent, zero-ambiguity results across sessions are critical for validating individual steps from a specification.
Spec execution returns a GAP status instead of FAILED when it detects the spec does not cover a specific scenario. This distinct result provides guidance on missing specifications, whereas FAILED indicates an execution attempt that did not succeed.
WesleyMFrederickGenerate implementation plans with exact file paths, code samples, and tests.
openshift-engAnalyze end-to-end test files to identify missing scenarios, platforms, and protocols.
xg-gh-25Execute deterministic health checks on SwarmAI subsystems and summarize pass/fail results for CI workflows.
mvillmowExecute Mojo or Pytest test suites and generate structured pass/fail reports.
