ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
Best use case
ctx-add-decision is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
Teams using ctx-add-decision should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-add-decision/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-add-decision Compares
| Feature / Agent | ctx-add-decision | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Record an architectural decision in DECISIONS.md. ## When to Use - After resolving a trade-off between alternatives - When making a non-obvious design choice - When the "why" behind a choice needs to be preserved ## When NOT to Use - Minor implementation details (use code comments instead) - Routine maintenance or bug fixes - When there was no real alternative to consider ## Decision Formats ### Quick Format (Y-Statement) > "In the context of **[situation]**, facing **[constraint]**, we decided > for **[choice]** and against **[alternatives]**, to achieve > **[benefit]**, accepting that **[trade-off]**." ### Full Format Gather: Context, Alternatives, Decision, Rationale, Consequence. ## Execution ```bash ctx add decision "Use Cobra for CLI framework" \ --context "Need CLI framework for Go project" \ --rationale "Better subcommand support, team familiarity" \ --consequence "More boilerplate, but clearer command structure" ``` ## Quality Checklist - [ ] Context explains the problem clearly - [ ] At least one alternative was considered - [ ] Rationale addresses why alternatives were rejected - [ ] Consequence includes both benefits and trade-offs
Related Skills
ctx-decision-add
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.