cognitive-doc-design

Restructure documentation to lead with answers and include verification checklists.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill cognitive-doc-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-doc-design
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/cognitive-doc-design
Command: npx skills add https://github.com/kurojs/EnderDots --skill cognitive-doc-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces reader confusion and reviewer burnout by structuring documentation so the key decisions and next actions are immediately visible.

Core Features & Use Cases

  • Lead with the answer to surface outcomes, decisions, and actions before context.
  • Progressive disclosure and chunking to make long technical material scannable and easier to verify.
  • Review empathy with checklists and signposting so readers can confirm intent without reconstructing the full story.
  • Use cases: PR descriptions, RFCs, onboarding/maintainer guides, architecture and workflow documentation, and any dense doc that needs to be easier to use during review.

Quick Start

Use the cognitive-doc-design skill to rewrite the provided document so it opens with the outcome, includes a Quick path, and ends with a verification checklist and next step.

Frequently Asked Questions about cognitive-doc-design

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

FAQPage Schema
How do I write architecture docs and PR descriptions that are easier to review?

Restructure dense architecture docs and PR descriptions using lead-with-the-answer formatting, progressive disclosure, and chunking to make decisions and actions immediately scannable for reviewers.

What is the best way to reduce cognitive load in technical writing?

Reduce cognitive load in technical writing by applying progressive disclosure and chunking, which breaks long material into scannable sections so readers can verify intent without reconstructing the full story.

How do I format an RFC so reviewers can quickly verify decisions?

Format RFCs with recognition-friendly checklists, signposting, and upfront outcomes, allowing reviewers to confirm intent and next actions quickly without reading dense contextual background.

Can I use this documentation restructuring method for onboarding guides?

Yes, the restructuring method works for onboarding guides, maintainer guides, and workflow documentation, transforming dense material into scannable content that surfaces outcomes and verification steps.

Does progressive disclosure work for dense code review notes?

Progressive disclosure works for code review notes by chunking dense technical material into scannable sections, ensuring review empathy and making verification steps immediately visible.

When should I not use chunking and signposting in documentation?

Avoid chunking and signposting for short, straightforward documents where lead-with-the-answer formatting is unnecessary, as progressive disclosure adds structural overhead to simple content.