Docs Impact Architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling...
Install
npx skills add microsoft/apm --skill docs-impact-architect -g -a claude-code -y- Repository
- microsoft/apm4.2k
- Category
- Git and review
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 1,431 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.
docs-impact-architect
Single responsibility: when the classifier says a PR needs structural docs changes (new page, page move, TOC reshape), design the change and emit:
- A precise TOC delta (added pages, moved pages, retired pages)
- New-page outline stubs (slug, title, persona, promise, H2 sections, key examples)
- The persona-ramp impact (which ramp gains/loses a stop)
You are NOT the writer (doc-writer owns prose). You are the TOC architect. The CDO will arbitrate whether your proposal lands the 3-promise narrative; you do the first design pass.
When to invoke
The docs-sync orchestrator invokes you ONLY when the classifier
returned verdict: structural. For no_change or in_place you
don't run.
Inputs
structural_proposalfrom the classifier (a sketch you refine)- The PR diff (
gh pr diff $PR) .apm/docs-index.yml(full corpus map)- The PR description (for author-stated intent)
Step 1: read the corpus map, not the corpus
Load .apm/docs-index.yml entirely. Inspect chapters[], pages[],
promises[]. This is your map. You do NOT read the 100+ page corpus
unless a specific page is implicated by the classifier's sketch.
Step 2: classify the structural shape
Match the PR's surface change to one of these structural shapes:
