Stats
Actions
Tags
From itteam
Log a decision to the current project's decisions-log.md with the next stable ID. Invokes the log-decision skill. Optional argument: the decision statement itself. Only for decisions already made — not for tentative or future decisions.
How this command is triggered — by the user, by Claude, or both
Slash command
/itteam:logThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /log
You are being asked to invoke the `log-decision` skill.
First, verify the request is actually for a decision that has been made — not a tentative thought, preference, or future plan. If the statement contains hedging words ("probably", "thinking about", "leaning toward", "I think", "tomorrow we'll") or is phrased in future tense, stop and reflect that back: "This sounds like a pending question rather than a decision. Should I add it to the project's open questions instead?"
If the user typed `/log` followed by a statement, treat that statement as the decision to log. Parse it to e...You are being asked to invoke the log-decision skill.
First, verify the request is actually for a decision that has been made — not a tentative thought, preference, or future plan. If the statement contains hedging words ("probably", "thinking about", "leaning toward", "I think", "tomorrow we'll") or is phrased in future tense, stop and reflect that back: "This sounds like a pending question rather than a decision. Should I add it to the project's open questions instead?"
If the user typed /log followed by a statement, treat that statement as the decision to log. Parse it to extract:
If the user typed /log with no argument, ask:
Then execute the log-decision skill:
decisions-log.md to determine the next D-NNN.If the user's statement appears to be an action item, open question, risk, or assumption (not a decision), stop and reflect that back — do not silently coerce it into a decision entry.
npx claudepluginhub shaybar1/itteam-cowork-plugins --plugin itteam/logLogs orchestrated task work including time spent, progress notes, and code stats to tools like Linear, Obsidian, Jira, or GitHub Issues. Supports task ID and destination options.
/logLogs orchestrated task work including time spent, progress notes, and code stats to tools like Linear, Obsidian, Jira, or GitHub Issues. Supports task ID and destination options.
/logInteractively logs AI experiments by gathering tool, prompt, summary, and rating details conversationally, then displays formatted terminal report with ID and stats.
/logCreates a structured technical session conversation log with sections for overview, decisions, work performed, outcomes, next steps, notes, and auto-generated tags.
/logInteractively gathers error details, cause, solution, rationale, code changes, and tags from context, then logs them to the error memory database via bash script.