Skip to content
cccskills
FreePublished on GitHub

decide

Record decisions in docs-agents/DECISIONS.md — add a TBD (open question), log a decided decision, or revise/revoke an existing one. Use when the user says "decide", "we decided", "log a decision", "that's TBD", or wants to change/revoke a past decision

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

decide

Maintains docs-agents/DECISIONS.md. Keep entries terse.

Locate the file

Edit docs-agents/DECISIONS.md in the current project. If it doesn't exist, create it with this structure:

# Decisions

## TBD

- **<Shortname> — <pending decision>** — options/context in one line.

## Decided

### DEC-001 — title

Decided by: Author | Author with Agent | Agent
Date: YYYY-MM-DD HH:MM

**Decision:** 1–2 sentences (what was decided).

**Rationale:** 1–2 sentences (why).

Modes

1. Add a TBD (open question requiring a decision to move forward, not yet decided). Not to be confused with an open question from docs-agents/QUESTIONS.md which do not related to decision. Append to the ## TBD list:

- **<Shortname> — <pending decision>** — options/context in one line.

2. Log a decided decision

  • Find the highest DEC-NNN in ## Decided; new id = highest + 1, zero-padded to 3 digits.
  • Prepend the new entry to the top of ## Decided (newest first).
  • Get the timestamp by running date "+%Y-%m-%d %H:%M".
  • If it resolves a ## TBD item, remove that TBD line.
### DEC-NNN — <title>

Decided by: Author | Author with Agent | Agent
Date: YYYY-MM-DD HH:MM

**Decision:** 1–2 sentences (what was decided).

**Rationale:** 1–2 sentences (why).

Set "Decided by" to who actually decided (ask if unclear; default Author with Agent). Author means the person using the skill. Agent means the coding agent harness in use.

3. Revise a decision Locate the DEC-NNN. Do NOT rewrite history silently — append a revision note under the existing entry:

**Revised (YYYY-MM-DD HH:MM):** what changed and why. Supersedes original decision above.

Then move the whole entry to the top of ## Decided. Keep its original id — the number is a stable reference, not a sort key, so recently-touched decisions surface first even if ids end up out of numeric order.

4. Revoke a decision Prefix the title with ~~REVOKED~~ and append:

**Revoked (YYYY-MM-DD HH:MM):** reason. No longer in effect.

Then move the whole entry to the top of ## Decided (same rule as revise) — a revocation is important activity, so surface the "no longer in effect" warning rather than leaving it buried.

Rules

  • Never renumber existing DEC ids.
  • Always stamp real timestamps via date, never guess.
  • Keep it skimmable — 1–2 sentences per field.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

commit

Free

Turn uncommitted work into a logically ordered sequence of atomic conventional commits. Surveys the whole working tree, groups changes, orders them foundation-first, shows a plan, then commits by path. Use when the user says "commit this", "commit my work", "split this into commits", or "clean up my changes into commits"

The English summary is being prepared. Showing the original description.

patrickfleith/awesome-spacecraft-engineering-datasets110Updated Oct 23, 2026

Manage docs-agents/GLOSSARY.md — add or refine a canonical term, extract terms from the current conversation, or audit for conflicts and duplicates. Use when the user says "define this term", "add to the glossary", "build a glossary", "what do we call this", or wants to harden terminology

The English summary is being prepared. Showing the original description.

patrickfleith/awesome-spacecraft-engineering-datasets110Updated Oct 23, 2026

log

Free

Quickly add one entry to the right doc — a task, idea, stack choice, concern, or open question — in the correct format. Triggered by "log"/"note"/"capture"/"add"/"jot down" + the kind, e.g. "log this task", "note this idea down", "capture a concern", "add TODO", "we're using X for Y — put it in the stack", "open question:". Addition only.

The English summary is being prepared. Showing the original description.

patrickfleith/awesome-spacecraft-engineering-datasets110Updated Oct 23, 2026

unslop

Free

Rules for AI-written text. Must always apply.

The English summary is being prepared. Showing the original description.

patrickfleith/awesome-spacecraft-engineering-datasets110Updated Oct 23, 2026

Write or update docs-agents/SUM.md — the Software User Manual — from the codebase. Mode 1 (generate) builds a full, detailed SUM from scratch by inventorying every user-facing surface so nothing is missed. Mode 2 (update) revises the SUM against a PR/diff, removing what's obsolete, editing what changed, and adding what's new — precisely and concisely. Triggered by "write the manual", "generate the user manual", "document how to use this", or "update the manual for this PR".

The English summary is being prepared. Showing the original description.

patrickfleith/awesome-spacecraft-engineering-datasets110Updated Oct 23, 2026

See all skills by patrickfleith

Report a problem with this skill