SkillVaultskills Browse all 1,000+ skills

Productivity · Version 1.1.0 · Reviewed 2026-08-02

Specification Implementation Orchestrator

Turn engineering context into a reliable artifact for specification execution and implementation phase orchestration with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Executes an approved specification through bounded implementation phases, tests, reviews, checkpoints, and integration. It grounds the decision in the approved specification, implementation plan, repository rules, task dependencies, file ownership, and validation gates and explicitly prevents agents optimizing local tasks while drifting from acceptance criteria or integrating phases before prerequisites pass.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Specification execution
  • Implementation phase orchestration
  • Plan-to-code traceability

How Specification Implementation Orchestrator works

You provide

Repository access, entry points, and the target change

It inspects

Real execution path for specification execution, not naming

It decides

A implementation phase orchestration explanation with safe change seams

You verify

Claims confirmed against code paths or a test

What it checks first

Specification Implementation Orchestrator executes an approved specification through bounded implementation phases, tests, reviews, checkpoints, and integration. It grounds the decision in the approved specification, implementation plan, repository rules, task dependencies, file ownership, and validation gates and explicitly prevents agents optimizing local tasks while drifting from acceptance criteria or integrating phases before prerequisites pass. Use it when the work involves Specification execution, Implementation phase orchestration, Plan-to-code traceability.

  1. The entry points and the data flow between them, which is the fastest way to build an accurate mental model.
  2. Where behavior is actually decided, rather than where it appears to be configured.
  3. Which parts change frequently, since those carry the most current knowledge and the most risk.
  4. The seams where a change can be made safely without a wide blast radius.

Failure modes it recognizes

  • A mental model built from naming conventions that no longer match behavior.
  • Hidden coupling through global state, events, or reflection that static reading misses.
  • Dead code that appears authoritative and misleads the reader.
  • Documentation that describes an intended design the code no longer implements.

Answers it will reject

  • Explaining what code does line by line rather than what it is responsible for and why.
  • Trusting comments and documentation over the executing code path.
  • Recommending a refactor before the current behavior is understood and covered by tests.

Decision rules it applies

  • Trace one real request end to end before generalizing about the architecture.
  • Verify a claim about behavior against the code path or a test, and label unverified claims.
  • Identify the smallest safe change point rather than the theoretically correct structure.

Evidence it asks for

  • Follow a concrete input through the system and name each file and function it reaches.
  • Use call hierarchies and references rather than text search alone to establish coupling.
  • Confirm behavior with an executable test before changing it.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for specification execution.
  2. Organize implementation phase orchestration around the reader's next decision or action rather than the source order.
  3. Draft plan-to-code traceability with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Specification execution assessment
  • Implementation phase orchestration decision and action plan
  • Plan-to-code traceability verification checklist

Evidence requirements

  • Source code, discussion, notes, or existing artifact
  • Audience, decision, and acceptance criteria
  • Repository conventions and constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the specification implementation orchestrator to our current specification execution work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with the approved specification, implementation plan, repository rules, task dependencies, file ownership, and validation gates. The highest-risk failure is agents optimizing local tasks while drifting from acceptance criteria or integrating phases before prerequisites pass. Treat the specification as the behavior contract and the plan as revisable execution guidance with explicit change control. Verify the result by mapping every acceptance criterion to code and passing evidence on the final integrated revision.

Boundaries and compatibility

Ideal for

  • Specification execution: produce a decision or artifact grounded in supplied evidence.
  • Implementation phase orchestration: produce a decision or artifact grounded in supplied evidence.
  • Plan-to-code traceability: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing repository behavior or decisions
  • Replacing review by the accountable owner

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.