rsun-capture-dec

Captures conversational decisions as structured DEC markdown knowledge nodes with frontmatter and references.

Updated May 20, 2026
One-click install
npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-capture-dec-ezonelai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rsun-capture-dec
Source: https://github.com/EZoneLai/claude-plugin-ronsunai-os/tree/main/commands/rsun-capture-dec
Command: npx skills add https://github.com/EZoneLai/claude-plugin-ronsunai-os --skill rsun-capture-dec-ezonelai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decisions made during conversations are usually lost; this Skill turns them into persistent, citable DEC knowledge nodes so future sessions can reference the decision, its rationale, and its scope. ## Core Features & Use Cases - Decision Capture: Confirms title, area, decision, rationale, and references, then writes a DEC-{AREA}-{NNN} markdown file with YAML frontmatter and relations. - Auto Numbering: Scans the decisions directory to assign the next sequential ID per area. - Validation & Indexing: Runs validate-citations.py and build-knowledge.py to keep the knowledge graph consistent. - Use Case: After agreeing to quote a client at 1.8x margin, say "capture dec" to persist the decision as DEC-ESTIMATE-003 linked to the relevant case and SOP nodes. ## Quick Start Tell the assistant to capture the decision we just made about the pricing margin as a DEC node.

Frequently Asked Questions about rsun-capture-dec

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

FAQPage Schema
How do I save a decision made in a chat conversation?

Trigger the skill with a phrase like "capture dec" or "save this decision", optionally followed by the decision text. It confirms the title, area, rationale, and references, then writes a DEC markdown node into the decisions directory.

What is the difference between a DEC and an ADR?

A DEC records a lightweight tactical decision for a single scenario, while an ADR documents architectural decisions affecting multiple modules with formal trade-off analysis. The skill suggests upgrading to an ADR when the content is strategic.

How are DEC node IDs generated?

IDs follow the format DEC-{AREA}-{NNN}, where AREA is an uppercase domain like ESTIMATE or CRM. The skill lists existing files in the decisions directory, finds the highest number for that area, and increments it.

What happens if a referenced node ID does not exist?

After writing the file, the skill runs validate-citations.py to check all references. If a referenced ID is missing, it warns the user that the ID may be mistyped or the target node has not been created yet.

When should I not use decision capture?

Do not use it for multi-option architectural trade-offs or long-term strategic choices; those belong in a formal ADR. It also should not trigger automatically without an explicit user request to record the decision.