Create paired functional + technical documentation under docs/functional/ and docs/technical/ following project conventions. Use when asked to add feature docs, capability docs, paired PM/engineering docs, or documentation that matches the NNN-topic paired set pattern.
Produces a matching pair of documents: an executive functional summary and a detailed technical companion, per .claude/rules/documents.md.
docs/functional/ + docs/technical/, same NNN-topic.md basename).NNN numberdocs/functional/ and docs/technical/ (e.g. filenames like , ).001-auth.md042-payments.mdNNN to the next unused integer, zero-padded to three digits (e.g. if the highest existing is 002, use 003). If either folder is missing or empty, treat its max as 0.argument-hint or feature name — so the pair is NNN-topic-slug.md.docs/plans/ entries that define the feature.docs/functional/NNN-topic.md.claude/rules/diagrams.md).../technical/NNN-topic.md).docs/technical/NNN-topic.mdsequenceDiagram.../functional/NNN-topic.md).# <Feature Title>), same basename (NNN-topic.md), and reciprocal Paired With markdown links..claude/rules/diagrams.md for diagram choice and scope.Copy this structure into docs/functional/NNN-topic.md and replace placeholders:
# <Feature Title>
**Audience**: Product Managers, Managers, Architects
**Status**: Draft | Published
**Date**: YYYY-MM-DD
**Paired With**: [Technical](../technical/NNN-topic.md)
## Overview
One paragraph. Architecture terms OK (API, agent, provider), no code.
## System Flow
One Mermaid flowchart — user-visible flow only.
## What This Enables
3–5 capability bullets.
## Why It Matters
One paragraph on business value.
Copy this structure into docs/technical/NNN-topic.md and replace placeholders:
# <Feature Title>
**Audience**: Architects, Engineers
**Status**: Draft | Published
**Date**: YYYY-MM-DD
**Paired With**: [Functional](../functional/NNN-topic.md)
## Overview
One paragraph. Code references OK.
## Component View
Mermaid flowchart of system components.
## Request Flow
Mermaid sequenceDiagram.
## Key Patterns
Code examples for non-obvious patterns only.
## Configuration Reference
Variable table.
## Source Files
File → purpose table.
All diagrams use Mermaid (see .claude/rules/diagrams.md): fenced code blocks with the mermaid language tag; functional docs use one high-level user flowchart; technical docs include at minimum a component flowchart and a sequence diagram.