cognitive-doc-design

Structure complex documentation with progressive disclosure, chunking, and signposting.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill cognitive-doc-design-zmynxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cognitive-doc-design
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/cognitive-doc-design
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill cognitive-doc-design-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reduce cognitive overload in documentation by transforming dense, difficult-to-review content into clear, structured, and easy-to-follow documents.

Core Features & Use Cases

  • Cognitive Documentation Design: Applies principles like progressive disclosure, chunking, signposting, and recognition over recall to improve readability.
  • Review-Friendly Writing: Creates PR descriptions, architecture docs, onboarding guides, and contributor documentation that make decisions easier to verify.
  • Use Case: Turn a complex architecture proposal into a concise document with a clear summary, quick path, decision tables, and verification checklist.

Quick Start

Use the cognitive-doc-design skill to rewrite this documentation so reviewers can quickly understand the decisions, workflow, and next steps.

Frequently Asked Questions about cognitive-doc-design

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

FAQPage Schema
How do I reduce cognitive load in technical documentation?

To reduce cognitive load in technical documentation, apply structured patterns like progressive disclosure, chunking, and signposting. This transforms dense, difficult-to-review content into clear, easy-to-follow documents that improve overall reader comprehension.

What is the best way to structure an architecture proposal for review?

The best way to structure an architecture proposal for review is to use decision-focused layouts. Include a concise summary, quick path, decision tables, and verification checklists to make architectural decisions easier for reviewers to understand and verify.

How do I write a README file that improves onboarding comprehension?

To write a README file that improves onboarding comprehension, apply cognitive design principles like recognition over recall and progressive disclosure. This organizes complex information into clear, reviewable patterns that help new contributors understand workflows faster.

Can I use structured document patterns for PR review materials?

Yes, you can use structured document patterns for PR review materials. Applying chunking and signposting to PR descriptions creates review-friendly content that makes technical decisions and code changes significantly easier for reviewers to verify.

When do I need decision-focused layouts in RFCs?

You need decision-focused layouts in RFCs when complex proposals require clear verification. Structuring RFCs with summaries, quick paths, and decision tables reduces cognitive overload, allowing reviewers to quickly understand proposed decisions and next steps.