organise-docs

Consolidate conversation decisions and rationale into repository documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/olliecrow/codex --skill organise-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organise-docs
Source: https://github.com/olliecrow/codex/tree/main/skills/organise-docs
Command: npx skills add https://github.com/olliecrow/codex --skill organise-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill captures and organizes valuable knowledge from conversations, ensuring that important decisions, rationale, and learnings are preserved and made accessible in the project's documentation.

Core Features & Use Cases

  • Automated Documentation: Consolidates insights from discussions into structured documentation.
  • Knowledge Management: Identifies and preserves key decisions, trade-offs, and invariants.
  • Use Case: After a complex debugging session where a specific issue and its resolution were discussed at length, this Skill can automatically generate a new documentation entry detailing the problem, the fix, and the rationale behind it.

Quick Start

Use the organise-docs skill to capture durable knowledge from this conversation into the project documentation.

Frequently Asked Questions about organise-docs

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

FAQPage Schema
How do I capture decisions and rationale from conversations into project documentation?

To capture conversation outcomes into project documentation, you consolidate active discussions into structured repository entries. This Skill automates that process by identifying key decisions, trade-offs, and invariants, then preserving them for future contributors.

What is the best way to consolidate technical writing and knowledge management from chat logs?

The best way to consolidate technical writing from chat logs is to autonomously apply high-confidence updates that resolve contradictions. This Skill captures durable knowledge by structuring scattered discussion insights into accessible repository documentation.

Can I automatically generate documentation entries after a complex debugging session?

You can automatically generate documentation entries after a complex debugging session. This Skill consolidates the discussed problem, its resolution, and the underlying rationale into a durable, structured knowledge entry for your repository.

How does knowledge management handle contradictions when consolidating conversation insights?

Knowledge management handles contradictions by consolidating conflicting insights during the documentation process. This Skill autonomously resolves contradictions and applies high-confidence updates to preserve valuable information, principles, and constraints accurately.

When do I need to capture durable knowledge and invariants for future contributors?

You need to capture durable knowledge and invariants for future contributors whenever active conversations produce important decisions, constraints, or trade-offs. This ensures that valuable project rationale is preserved in documentation rather than lost.