Decision Log
Document a decision for "$ARGUMENTS" with full context, alternatives considered, and rationale. Capture the decision question, constraints, options evaluated, final choice, and conditions for revisiting.
See also /legal-decision-memo for recording a legal decision with its accepted risk and approvers, rather than a project or technical call.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"project-management-decision-log","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill. It can be run at any time, with or without existing project artifacts.
If .singularskills/project-management/<project>/ exists, read any available artifacts for context. If it does not exist, proceed based on information the user provides.
Process
Gather context:
- If
.singularskills/project-management/<project>/decision-log.md exists, read it for previous decisions and established patterns
- If
.singularskills/project-management/<project>/ exists, read available artifacts for project scope and constraints
- Understand what decision needs to be made — ask the user if not clear
Capture the decision question clearly:
- Frame the decision as a specific question: "Should we X or Y?" or "How should we approach Z?"
- A vague decision question leads to a vague decision — sharpen it until it is precise
- Note the urgency: is this blocking work? can it wait for more information?
- Identify who needs to be involved in making this decision
Document context and constraints:
- Why is this decision needed now? — what triggered it (new requirement, technical discovery, timeline pressure, team feedback)
- What constraints apply? — budget, timeline, technical limitations, team skills, organizational policies, compliance requirements
- What assumptions are we making? — state them explicitly so they can be challenged
- What do we already know? — relevant data, prior experience, industry standards, previous decisions that constrain this one
- What don't we know? — gaps in information, uncertainties that affect the decision
List alternatives considered (minimum 2-3):
- Always include at least 2-3 genuine alternatives — if there is only one option, the decision is already made
- Include "do nothing" or "defer" as an explicit option when applicable
- For each alternative, provide a brief description of what it entails
- Ensure alternatives are meaningfully different, not just minor variations
Evaluate each alternative with pros and cons:
- For each alternative, list:
- Pros — benefits, advantages, what it enables
- Cons — drawbacks, risks, what it costs or constrains
- Effort — rough estimate of implementation cost (time, money, complexity)
- Reversibility — how easy is it to change course later? (one-way door vs. two-way door)
- Use consistent evaluation criteria across all alternatives for fair comparison
- Note any strong opinions or preferences from team members or stakeholders
Record the final decision and rationale:
- State the decision clearly in one sentence
- Explain why this option was chosen over the others — what tipped the balance?
- Acknowledge trade-offs: what are we giving up with this choice?
- If the decision was contentious, note dissenting views respectfully
- Record the decision-making method used (consensus, leader decides, majority vote, delegation)
Note who made or approved the decision and when:
- Decision maker(s) — who had the final say
- Consulted — who provided input
- Informed — who needs to know about this decision
- Date — when the decision was made
- Effective date — when the decision takes effect (if different from decision date)
Define review and revisit conditions:
- Under what circumstances should this decision be reconsidered?
- Examples: "If X assumption proves wrong," "If costs exceed Y," "After Z months of experience," "If the team grows beyond N people"
- Set a review date if applicable (e.g., "Revisit in 3 months")
- Note any one-way-door aspects: after what point is this decision effectively irreversible?
Tag with relevant area:
- Categorize the decision: architecture, process, product, team, tooling, vendor, security, compliance, or other relevant area
- Tags help when searching for related decisions later
Write the artifact — append to .singularskills/project-management/<project>/decision-log.md under a ## Decision [N]: [Decision Title] section. Create the file with a # Decision Log — <project> heading if it does not exist; if a ## Decision [N]: [Decision Title] section already exists, replace only that section. The section contains:
- Date — when the decision was made
- Status — decided, superseded, or under review
- Area — category tag
- Question — the decision question
- Context — constraints and background
- Alternatives Considered — each option with pros, cons, effort, and reversibility
- Decision — the chosen option and rationale
- Decision Makers — who decided, consulted, and informed
- Revisit Conditions — when to reconsider
Output
Decision appended to .singularskills/project-management/<project>/decision-log.md. Present a summary highlighting:
- Decision question and chosen option
- Key rationale (why this over alternatives)
- Main trade-off acknowledged
- Revisit conditions
1---2name: project-management-decision-log3description: Document a project decision — question, constraints, alternatives with pros, cons and reversibility, the choice and rationale, and when to revisit. Use when the team has made or is making a project, technical or process call and wants a record of why. Not for a legal call and its accepted risk, or coaching on a management call; see /legal-decision-memo or /leadership-decision.4metadata:5 source: https://skillmd.com/skills/bromso/project-management-decision-log6 argument-hint: "[project] [--skip-checks]"7---89# Decision Log1011Document a decision for "$ARGUMENTS" with full context, alternatives considered, and rationale. Capture the decision question, constraints, options evaluated, final choice, and conditions for revisiting.1213See also `/legal-decision-memo` for recording a legal decision with its accepted risk and approvers, rather than a project or technical call.1415**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"project-management-decision-log","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1617## Prerequisites1819None — this is a utility skill. It can be run at any time, with or without existing project artifacts.2021If `.singularskills/project-management/<project>/` exists, read any available artifacts for context. If it does not exist, proceed based on information the user provides.2223## Process24251. **Gather context:**26 - If `.singularskills/project-management/<project>/decision-log.md` exists, read it for previous decisions and established patterns27 - If `.singularskills/project-management/<project>/` exists, read available artifacts for project scope and constraints28 - Understand what decision needs to be made — ask the user if not clear29302. **Capture the decision question clearly:**31 - Frame the decision as a specific question: "Should we X or Y?" or "How should we approach Z?"32 - A vague decision question leads to a vague decision — sharpen it until it is precise33 - Note the urgency: is this blocking work? can it wait for more information?34 - Identify who needs to be involved in making this decision35363. **Document context and constraints:**37 - **Why is this decision needed now?** — what triggered it (new requirement, technical discovery, timeline pressure, team feedback)38 - **What constraints apply?** — budget, timeline, technical limitations, team skills, organizational policies, compliance requirements39 - **What assumptions are we making?** — state them explicitly so they can be challenged40 - **What do we already know?** — relevant data, prior experience, industry standards, previous decisions that constrain this one41 - **What don't we know?** — gaps in information, uncertainties that affect the decision42434. **List alternatives considered (minimum 2-3):**44 - Always include at least 2-3 genuine alternatives — if there is only one option, the decision is already made45 - Include "do nothing" or "defer" as an explicit option when applicable46 - For each alternative, provide a brief description of what it entails47 - Ensure alternatives are meaningfully different, not just minor variations48495. **Evaluate each alternative with pros and cons:**50 - For each alternative, list:51 - **Pros** — benefits, advantages, what it enables52 - **Cons** — drawbacks, risks, what it costs or constrains53 - **Effort** — rough estimate of implementation cost (time, money, complexity)54 - **Reversibility** — how easy is it to change course later? (one-way door vs. two-way door)55 - Use consistent evaluation criteria across all alternatives for fair comparison56 - Note any strong opinions or preferences from team members or stakeholders57586. **Record the final decision and rationale:**59 - State the decision clearly in one sentence60 - Explain why this option was chosen over the others — what tipped the balance?61 - Acknowledge trade-offs: what are we giving up with this choice?62 - If the decision was contentious, note dissenting views respectfully63 - Record the decision-making method used (consensus, leader decides, majority vote, delegation)64657. **Note who made or approved the decision and when:**66 - **Decision maker(s)** — who had the final say67 - **Consulted** — who provided input68 - **Informed** — who needs to know about this decision69 - **Date** — when the decision was made70 - **Effective date** — when the decision takes effect (if different from decision date)71728. **Define review and revisit conditions:**73 - Under what circumstances should this decision be reconsidered?74 - Examples: "If X assumption proves wrong," "If costs exceed Y," "After Z months of experience," "If the team grows beyond N people"75 - Set a review date if applicable (e.g., "Revisit in 3 months")76 - Note any one-way-door aspects: after what point is this decision effectively irreversible?77789. **Tag with relevant area:**79 - Categorize the decision: architecture, process, product, team, tooling, vendor, security, compliance, or other relevant area80 - Tags help when searching for related decisions later818210. **Write the artifact** — append to `.singularskills/project-management/<project>/decision-log.md` under a `## Decision [N]: [Decision Title]` section. Create the file with a `# Decision Log — <project>` heading if it does not exist; if a `## Decision [N]: [Decision Title]` section already exists, replace only that section. The section contains:83 - **Date** — when the decision was made84 - **Status** — decided, superseded, or under review85 - **Area** — category tag86 - **Question** — the decision question87 - **Context** — constraints and background88 - **Alternatives Considered** — each option with pros, cons, effort, and reversibility89 - **Decision** — the chosen option and rationale90 - **Decision Makers** — who decided, consulted, and informed91 - **Revisit Conditions** — when to reconsider9293## Output9495Decision appended to `.singularskills/project-management/<project>/decision-log.md`. Present a summary highlighting:96- Decision question and chosen option97- Key rationale (why this over alternatives)98- Main trade-off acknowledged99- Revisit conditions