docs-impact-architect

Design structural documentation changes from PR impact analysis.

4|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/githubnext/apm --skill docs-impact-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-impact-architect
Source: https://github.com/githubnext/apm/tree/main/.apm/skills/docs-impact-architect
Command: npx skills add https://github.com/githubnext/apm --skill docs-impact-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The docs-impact-architect Skill automates the process of designing and proposing structural changes to documentation, such as adding new pages, moving pages, and reshaping the TOC, based on the impact analysis from a PR.

Core Features & Use Cases

  • TOC Delta Proposals: Generates precise TOC delta suggestions (new pages, moved pages, retired pages).
  • New-Page Outlines: Emits new-page outline stubs with necessary structure.
  • 3-Promise Narrative and Persona Ramps: Enforces the hard constraints of the 3-promise narrative and persona ramps.

Quick Start

Run the skill with the PR identifier to generate structural documentation changes: docs-impact-architect --pr <PR-id>

Frequently Asked Questions about docs-impact-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate TOC adjustments based on PR impact analysis?

You can automate TOC adjustments by running the docs-impact-architect skill with a PR identifier. It processes the PR diff and classifier verdict to generate precise TOC delta suggestions, including new, moved, and retired pages.

What is a 3-promise narrative in documentation structure?

A 3-promise narrative is a hard structural constraint enforced during documentation generation. It ensures new-page outlines and TOC adjustments follow a specific narrative framework and include persona ramps to guide the reader's journey.

How do I generate new-page outlines from a pull request diff?

To generate new-page outlines from a PR diff, provide the PR identifier to the skill. It analyzes the PR impact and emits structural outline stubs that align with the required documentation framework and persona ramps.

Do I need a classifier verdict to automate documentation structural changes?

Yes, a classifier verdict is a required constraint. The skill relies on both the classifier verdict and the PR diff to accurately design and propose structural changes such as TOC adjustments and new-page outlines.

Can I propose retiring or moving documentation pages based on code changes?

Yes, the skill analyzes PR impact to propose structural changes including moving and retiring pages. It generates TOC delta proposals that identify exactly which pages should be moved, retired, or added based on the code diff.

What are the limitations of automating TOC delta proposals with PR diffs?

The skill is constrained by requiring both a PR diff and a classifier verdict as inputs. Additionally, all generated structural outlines must strictly adhere to the 3-promise narrative and persona ramp constraints.