docs-impact-architect Skill
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 / produc Published by microsoft in apm.
What is docs-impact-architect Skill?
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 / produc Published by microsoft in apm. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Design and media
- Documentation use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use docs-impact-architect Skill
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/apm
- Skill file: .agents/skills/docs-impact-architect/SKILL.md
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 / produc
Skill instructions
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: 1. A precise TOC delta (added pages, moved pages, retired pages) 2. New-page outline stubs (slug, title, persona, promise, H2 sections, key examples) 3. 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 nochange or inplace you don't run. Inputs - structuralproposal from 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
Explore related resources
Frequently asked questions
What is docs-impact-architect?
docs-impact-architect is a open-source AI agent skill with Copy skill directory. Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR.
Who is docs-impact-architect best for?
docs-impact-architect is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows.
How do I install docs-impact-architect?
Install or run docs-impact-architect using Copy skill directory. Check docs-impact-architect for the latest setup command.
Is docs-impact-architect actively maintained?
docs-impact-architect may need a closer maintenance check before production use.
Auto-fetched from GitHub.
