API Integration
Webhook handling, rate limits, error codes, idempotency. The edge cases that sink API integrations before they launch.
Mobile Feature
Platform differences, offline states, permissions, accessibility. More surface area than web — this template covers it.
Onboarding Flow
Step sequence, skip logic, analytics events, re-entry behavior. The details that determine whether users activate.
Payment Integration
PCI constraints, webhook confirmation, failed payment recovery. The highest-stakes feature a team ships.
Dashboard Redesign
Backward compatibility, filter state, empty states, partial failures. The questions users notice when they're answered wrong.
About these templates
Each template covers the same core structure: problem statement, scope, key behaviors, edge cases, open questions, and a coding agent context block. The coding agent context section — covering tech stack, reference files, patterns to follow, hard constraints, and testable acceptance criteria — is what makes these templates different from standard spec formats.
A human developer can infer most of this from experience and conversation. A coding agent cannot. These templates surface what the agent needs to know before build starts — not after it returns something that almost fits.