Tech Spec

A tech spec is a typed call-stack architecture handoff: code-shaped contracts plus execution flows. Prefer TypeScript pseudocode over prose wherever precision matters.

Treat ../coding-standards/ as the standards package and ../tdd/ as the testing workflow.

This skill is design-only. Do not implement. Save a file only when the user asks for a file; otherwise return the spec inline.

Branch selection

1. Use Path A: Convert context to spec when the conversation, docs, or codebase already contain enough background to describe the change.
2. Use Path B: Grill first when the user wants a new spec but has not provided enough problem, constraints, design direction, affected code, or acceptance criteria.

If a question can be answered by exploring the codebase, inspect the codebase instead of asking.

Completion criterion: the branch is chosen from actual available context; missing architectural decisions are not invented.

Path A: Convert context to spec