Maintain system and domain architecture docs such as docs/ARCHITECTURE.md, web-architecture.md, or api-architecture.md. Use when topology, shared patterns, cross-component flows, deployment model, or ownership boundaries change.
Maintain technical design docs for services, components, workers, modules, and APIs. Use when implementation design, contracts, schema, integrations, runtime behavior, or operational concerns change.
Maintain feature docs that explain user-visible behavior, goals, flows, and business rules without implementation detail. Use when feature scope, user workflows, or product behavior changes.
Create and maintain evidence-based Product Requirements Documents (PRDs). Use when writing, reviewing, or revising product requirements, initiative scope, success measures, or product decisions before technical design and delivery planning.
Create and maintain outcome-driven product roadmaps. Use when defining, reviewing, or revising product priorities, strategic themes, Now/Next/Later horizons, roadmap phases, dependencies, or criteria for changing direction.
Use when generating, decomposing, creating, or updating implementation tasks in Linear through the official Linear MCP. Requires a reviewed preview before every mutation.