implement-spec
Execute an approved specification and its authorized tickets, integrating and verifying the complete result.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- implement-spec
- description
- Execute an approved specification and its authorized tickets, integrating and verifying the complete result.
02 资源文件 1
- 参考文档agents/openai.yaml276 B
03 SKILL.md 正文
Implement Spec
Use coding-orchestration as the only router, including its Session selection
and role ownership section. Read the approved spec and resolve
its authorized ticket set and dependencies. Use the pure orchestration-plan
operation when dependencies or disjoint ownership need an explicit frontier.
For an ordinary bounded change, execute directly through the same router.
The user's request may authorize a named spec and its scoped tickets; the user need not recite IDs or repeat retained authorization. The planner only returns eligibility and topology: it never authenticates authority or launches writers. Before dispatch, the parent verifies that the repository, revision, ticket IDs, owned surfaces, protected boundaries, and requested operation still match the current user instruction.
Run eligible work with one writer by default. Use isolated worktrees when needed
for safe ownership, not as a mandatory worktree per ticket. Each writer gets an
exact root, bounded scope, focused checks and terminal state. Carry approved
visual references through design-direction before UI dispatch. Recompute an
explicit frontier after integration when used. The parent owns integration,
conflicts, applicable integration checks, corrections and final judgment.
Preserve operation-specific authority for publication, merge, release, production, external writes, paid services and destructive cleanup. Use current and retained user authorization with the repository policy; do not request a settled approval again. Prepare reversible local work and the reviewable candidate before stopping for a genuinely missing external-operation authorization.
This adapter preserves the useful task-graph pattern from Matt Pocock's
upstream implement-spec snapshot while replacing its delivery semantics with
the Development System contract.
04 同仓库更多 Skills
working-backwards
Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.
flow-implement
Implement a requested software change through verification, corrections, and its authorized delivery endpoint.
development-steward
Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.
grill-with-docs
Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.
global-agent-guardrails
Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.
impeccable
Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.