docs-development

Develop `.carta/` documentation through stepwise growth from simplest working docs.

1|Updated Jan 19, 2026

Search Tags:#documentation #adr #workspace #specs #carta #unfolding #product modeling

Ready to run

npx skills add https://github.com/saxonthune/carta --skill docs-development-saxonthune

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-development
Source: https://github.com/saxonthune/carta/tree/main/.claude/skills/docs-development
Command: npx skills add https://github.com/saxonthune/carta --skill docs-development-saxonthune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you develop a deterministic .carta/ documentation workspace by building the simplest working version first and then expanding it only as needed.

Core Features & Use Cases

Unfolding-first doc growth: Starts with purpose and happy path, then grows detail through real use rather than premature scaffolding.
4-title model guidance: Helps you choose and operate at the correct abstraction level (product strategy, product design, architecture, or code shapes).
Session continuity: Encourages tracking decisions and open questions so the next development session builds on what’s already settled.
Stress-testing at the right time: Adds edge-case validation only when the happy path is stable or handoff to implementation is imminent.
Doc-only assistance: Focuses on writing and refining documentation, not generating source code.

Quick Start

Use the docs-development skill to turn your current one-sentence product purpose into the next minimal happy-path .carta/ doc that can be expanded in future sessions.

Frequently Asked Questions about docs-development

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

FAQPage Schema

How do I build documentation incrementally without scaffolding too much detail upfront?▼

Incremental documentation development starts with the simplest working docs, covering purpose and the happy path, then expands detail through real use rather than adding premature scaffolding.

What is the 4-title model for product documentation and how does it guide abstraction levels?▼

The 4-title model categorizes documentation across product strategy, product design, architecture, and code shapes, guiding you to author and refine docs at the correct abstraction level for each specific task.

When should I add edge-case validation and stress-testing to my workspace specs?▼

Edge-case validation and stress-testing should be added to workspace specs only when the happy path is stable or when handoff to implementation is imminent, avoiding premature architecture or error enumeration.

Can I generate source code alongside authoring product modeling documentation?▼

No, this documentation workflow focuses strictly on doc-only assistance, meaning it helps you author and refine documentation without generating source code or enumerating premature architecture.

How do I track decisions and open questions for session continuity in documentation?▼

Session continuity in documentation is maintained by tracking decisions and open questions within the workspace, ensuring the next development session builds directly on what was already settled previously.