write-tech-spec

To write a tech spec for cross-module architecture, draft a TECH.md file translating product intent into an implementation plan that documents API choices and fits the existing codebase. This structured template explicitly guides reviewers with required context, proposed changes, and validation criteria.

A TECH.md specification for implementation planning must include Context, Proposed changes, and Testing and validation sections. It should reference the PRODUCT.md for behavior anchors and document architectural choices to make the work easier for agents to execute and reviewers to evaluate.

You need a formal tech spec for codebase development when a feature spans multiple modules like UI, core runtime, and networking. This cross-module architectural work requires detailed design and review to outline required APIs and milestones before implementation begins.

To translate product intent into a codebase implementation plan, draft a TECH.md spec based on current codebase research. It anchors product behavior to the PRODUCT.md and translates that intent into a structured plan fitting the existing architecture.

Yes, this tech spec template works for features spanning UI, core runtime, and networking. It provides a structured template for cross-module architectural planning, outlining required APIs and milestones to guide reviewers evaluating the significant feature.

The best way to document architectural choices for agent execution is to draft a TECH.md specification outlining required APIs, milestones, and validation criteria. This makes the implementation work easier for agents to execute and reviewers to evaluate.