implement-spec

Executes approved specifications and authorized tickets through coordinated writer dispatch and integration.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill implement-spec-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/implement-spec
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill implement-spec-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved specification and its authorized ticket set into verified, integrated code changes without losing track of ownership, dependencies, or authorization boundaries. ## Core Features & Use Cases - Ticket Resolution and Planning: Reads the approved spec, resolves its authorized tickets and dependencies, and uses an orchestration-plan operation when an explicit execution frontier is needed. - Bounded Writer Dispatch: Runs eligible work with one writer by default, giving each writer an exact root, bounded scope, focused checks, and a defined terminal state, with isolated worktrees when ownership requires them. - Parent-Owned Integration: The parent owns integration, conflict resolution, integration checks, corrections, and final judgment, while preserving user authority for publication, merge, release, and destructive operations. - Use Case: After a spec and its tickets are approved, instruct the agent to implement the spec; it verifies repository, revision, ticket IDs, and protected boundaries, dispatches writers, integrates results, and stops only when a genuinely missing external-operation authorization is required. ## Quick Start Implement the authorized specification using its current references, bounded ownership, focused checks and requested delivery state.

Frequently Asked Questions about implement-spec

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

FAQPage Schema
How do I implement an approved specification with AI agents?▼

Authorize the named spec and its scoped tickets, then let the skill resolve dependencies and dispatch bounded writers through the coding-orchestration router. The parent agent verifies repository, revision, ticket IDs, and protected boundaries before dispatch and owns integration afterward.

How does ticket dependency planning work before dispatching writers?▼

The orchestration-plan operation returns eligibility and topology for the authorized ticket set, producing an explicit execution frontier when dependencies or disjoint ownership require it. It never authenticates authority or launches writers itself.

Does each ticket need its own isolated worktree?▼

No. Eligible work runs with one writer by default, and isolated worktrees are used only when needed for safe ownership, not as a mandatory worktree per ticket. Each writer still receives an exact root, bounded scope, and focused checks.

Who owns integration and conflict resolution after writers finish?▼

The parent agent owns integration, conflict resolution, applicable integration checks, corrections, and final judgment. When an explicit frontier was used, it is recomputed after integration to confirm remaining work.

When does the skill stop and ask for additional authorization?▼

It stops only for genuinely missing external-operation authorization, such as publication, merge, release, production writes, paid services, or destructive cleanup. Settled approvals are not requested again; reversible local work and a reviewable candidate are prepared first.