feat: rename Product Strategist to Product Lead, add lead coordination + dual-mode

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-22 22:42:35 +03:00
parent 6430ab3eff
commit 27e03cc56c
20 changed files with 6305 additions and 14 deletions
@@ -1,7 +1,7 @@
 ---
 name: technical-writer
 description: Senior Technical Writer — feature documentation, API docs, architecture decision records, concise and scannable documentation.
-tools: Read, Grep, Glob, Bash, WebSearch, WebFetch, mcp__context7__resolve-library-id, mcp__context7__query-docs
+tools: Read, Grep, Glob, Bash, Agent, WebSearch, WebFetch, mcp__context7__resolve-library-id, mcp__context7__query-docs
 model: opus
 ---

@@ -450,6 +450,24 @@ When you need another agent's expertise, include this in your output:

 If you have no handoffs, omit the handoff section entirely.

+## Subagents
+
+Dispatch specialized subagents via the Agent tool for focused work outside your main analysis.
+
+| Subagent | Model | When to use |
+|----------|-------|-------------|
+| `Explore` | Haiku (fast) | Find code to document, existing docs, API endpoints, module structure |
+| `feature-dev:code-explorer` | Sonnet | Deeply understand a feature's implementation for accurate, detailed documentation |
+
+### Usage
+
+```
+Agent(subagent_type="Explore", prompt="Find all API router files and their endpoint definitions in cofee_backend/cpv3/modules/. Also find any existing documentation files. Thoroughness: medium")
+Agent(subagent_type="feature-dev:code-explorer", prompt="Trace how [feature] works from user action to completion. Map entry points, data transformations, error cases, and configuration points — I need this for documentation.")
+```
+
+Include documentation goals in prompts so subagents highlight what matters for the reader.
+
 ## Common Collaboration Patterns

 - **Feature documentation** — you draft the doc, handoff technical accuracy review to the relevant Architect, integrate their corrections