Skip to content
cccskills
FreePublished on GitHub

log

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.

See how to install

Files included (1)

  • SKILL.md3.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

log

Append a single new entry to the correct doc under docs-agents/, in that doc's format. This skill only adds — it never edits, reorders, or removes existing entries. Decisions and glossary terms are out of scope (use decide / glossary).

Route by what the user is logging

Match on the kind the user names, however they phrase it (log / note / capture / add / jot down / write down / remember, or just naming the thing):

Kind & example phrasingsFileWhat to do
task — "log this task", "add a TODO", "remind me to…", "we still need to…"docs-agents/TASKS.mdcheckbox item at top of To do
idea — "log this idea", "note this down", "what if we…", "idea:"docs-agents/IDEAS.mdnew IDEA-NNN at the top
stack — "we're using X for Y", "put X in the stack", "we went with X"docs-agents/STACK.mdadd a - **Category:** choice bullet
concern — "log this concern", "I'm worried that…", "flag that…", "risk:"docs-agents/CONCERNS.mdnew CON-NNN at the top
question — "log this question", "open question:", "we need to figure out…"docs-agents/QUESTIONS.mdnew Q-NNN at the top

Newest goes on top. Insert each new entry above the existing ones, not at the bottom. (Stack is the exception — it's grouped by category, not by recency.)

If the target file doesn't exist, create it with just its # Heading before adding the entry. For ID'd docs, next id = highest existing NNN + 1, zero-padded to 3.

Formats

Task — docs-agents/TASKS.md, insert at the top of the ## To do section:

- [ ] <task> <!-- optional (context) -->

The file is organized ## To do / ## Done. Create those sections if missing; leave completed items alone (they belong under ## Done).

Idea — docs-agents/IDEAS.md, insert at top of the list (newest first):

## IDEA-NNN — <one-line title>

Brief note (10–50 words), or bullets.

Stack — docs-agents/STACK.md, add a bullet in its logical spot (grouped by category, parentheses only if extra detail helps):

- **<Category>:** <choice> (<detail>)

If that category already exists with a different value, don't overwrite — flag the conflict and ask.

Concern — docs-agents/CONCERNS.md, insert at top (newest first):

## CON-NNN — <one-line title>

What it is and why it matters (10–50 words). Ref: <url, if any>

Question — docs-agents/QUESTIONS.md, insert at top (newest first):

## Q-NNN — <the question> — `open`

**Answer:** <fill once answered; set status to `answered`>

Rules

  • One entry per invocation, inserted at the top — no rewriting the rest of the file.
  • Keep it tight. Fit the format; don't pad. Rephrase the user's note only enough to be clear.
  • Never guess an id — read the file, find the highest, increment.
  • Ambiguous target? If it's unclear which doc the user means, ask before writing.

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

decide

Free

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.

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

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