Skip to main content

​
What We Learned

The a2a spec-to-package pattern (documented in the fingerprint session) extends to multi-document synthesis. The CLI prompt referenced three separate sources simultaneously:
  1. Handbook Section 9 — command table with 13 commands, exit codes, and flags (the full reference)
  2. TAD Layer 5 — detailed per-command specifications with flags, outputs, and behaviours (the architecture)
  3. Synthesis Strategy Section 4 Phase 1 — MVP scoping that reduced 13 commands to 7 (the constraint)
The agent’s plan mode resolved the three documents into a single coherent implementation plan before writing any code. The scoping constraint from the synthesis document was load-bearing — without it, the agent would have implemented all 13 commands.

​
The Pattern Extension

The fingerprint session’s pattern was [spec-reference] → [API surface] → [test requirements]. The CLI session adds a fourth element: [cross-document resolution with explicit scoping]. 
Read [doc A] section N (for command reference)
Read [doc B] layer M (for detailed specifications)
Read [doc C] section P phase Q (for MVP scoping)
Scaffold @stratt/cli implementing the MVP-scoped commands from doc C,
with specifications from doc B and exit codes from doc A.
The explicit scoping document prevents scope creep. Without it, the agent plans from the most complete specification and builds everything.

​
Why It Matters

Implementation velocity for CLI tools is bottlenecked by specification reconciliation, not by code generation. When the agent can cross-reference multiple documents and resolve contradictions during planning (not during coding), the implementation is coherent on the first pass. The STRATT CLI had zero architectural rework — the plan phase absorbed all the spec reconciliation.

​
Applicability

This pattern works when: (a) the specification is split across multiple documents with different purposes (reference vs architecture vs scoping), (b) the documents were written at different times and may have divergences, (c) the MVP scope is a strict subset of the full specification. The prompt must name the scoping document explicitly or the agent defaults to the most complete spec.