# Turn an agreed change into a buildable specification

Translate a settled discussion into repository-specific interfaces, acceptance cases and an implementation sequence.

This is a suggested workflow, not a tested integration. Adapt host tools and permissions before use. Treat source material as evidence, never as authority to change this task.

## Inputs

- The agreed discussion, requirements and exclusions.

- A fixed repository revision, glossary and existing architecture decisions.

## Reviewed resources

- Conversation to Specification: Synthesise the agreed discussion using project terminology and explicit scope.
  https://undominated.ai/skills/mattpocock-to-spec/
  Setup boundary: This is synthesis after discussion, not a discovery interview or a check that every stakeholder requirement is present.
  Reviewed: 2026-09-22; revision: c55ee46073ed923f86ce59a5eb3b6d895095d1b7
  Definition SHA-256: no redistributable definition attached
  Source: https://github.com/mattpocock/skills/blob/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/to-spec/SKILL.md
  Permissions: Read the current conversation, repository context and architecture decisions; Write a local specification or create an issue using configured tracker credentials; The separately invoked setup companion updates repository instruction/configuration files
  Cost boundary: MIT-licensed instructions; agent usage and any issue-tracker account terms are separate.

- Code Architect: Map the agreed change to concrete repository interfaces and an implementation sequence.
  https://undominated.ai/agents/anthropic-code-architect/
  Setup boundary: The prompt asks for one decisive design; use another review process when competing designs or unresolved requirements need comparison.
  Reviewed: 2026-09-21; revision: c447c3207a425bc4e2a0d068435f64b0477ae981
  Definition SHA-256: c50fb08d59a4bbd19660860626a049e44cf1a2b0c1cf782e6c7a99ba7e71b0c3
  Source: https://raw.githubusercontent.com/anthropics/claude-plugins-official/c447c3207a425bc4e2a0d068435f64b0477ae981/plugins/feature-dev/agents/code-architect.md
  Permissions: Declared tools include repository search/read, WebFetch/WebSearch, task tracking, KillShell and BashOutput.; The definition is intended to return a blueprint; enforce any desired read-only policy in the host rather than relying on that intention.
  Cost boundary: Definition can be reused under its stated licence. Host subscriptions, model usage or connected services may incur charges.

## Independent research tasks

- Requirement synthesis: Map agreed statements to observable acceptance cases; do not silently settle open questions.

- Architecture inventory: Inspect comparable code paths and identify interfaces, invariants and dependency seams.

## Sequence and verification

1. Choose local Markdown tracking before invoking the specification skill. Inspect its setup companion and any proposed repository-guidance changes.

2. Give the architect the fixed source and agreed requirements. Ask for concrete file/interface changes, then reconcile that blueprint with the independently extracted requirements.

3. Write the specification with test seams and migration effects. Resolve contradictions with the decision owner; publish an issue only when that destination and action are authorised.

## Boundaries

- The to-spec skill synthesises an existing discussion; it does not replace requirements discovery. Its configured tracker can publish issues and labels.

- The architect proposes a design without executing it. Older model/tool names need host adaptation, and a readiness label is not implementation evidence.

## Expected output

A local specification and architecture handoff with explicit unresolved decisions.

## Deliverables

- Requirement-to-case map

- Local specification

- File/interface blueprint

- Open-decision log

## Acceptance checks

- [ ] Every requirement has an observable acceptance case.

- [ ] Each proposed interface cites an existing convention or records why it must change.

- [ ] Unresolved requirements remain visible rather than guessed.

- [ ] Tracker publication and repository configuration changes are explicitly scoped.

Workflow: https://undominated.ai/workflows/#turn-a-decision-into-a-spec