ワンクリックでManusで任意のスキルを実行

decision-memo-writer

スター6

フォーク1

更新日2026年3月2日 12:20

Produces structured decision records with rationale, alternatives considered, and consequences. Use when recording non-trivial decisions that future team members need to understand.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vibbs

vibbs/company-os

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Decision Memo Writer

Reference

ID: S-ORG-02
Category: Orchestration
Inputs: decision context, alternatives, stakeholder positions
Outputs: decision memo artifact → artifacts/decision-memos/
Used by: Orchestrator Agent
Tool scripts: ./tools/artifact/validate.sh

Purpose

Records non-trivial decisions with full rationale, alternatives evaluated, and anticipated consequences so that future team members can understand why a particular path was chosen without re-litigating the discussion.

Procedure

ID Convention

Use the format DM-{NNN} for decision memo IDs (e.g., DM-001, DM-002). For specialized memos, use prefixes:

REVIEW- for review memos (e.g., REVIEW-WEEKLY-2026-03-01)
RETRO- for retrospective memos (e.g., RETRO-PRD-001)
GROWTH- for growth experiment memos (e.g., GROWTH-001)
CONV- for customer conversation logs (e.g., CONV-001)

Check artifacts/decision-memos/ for existing IDs to avoid collisions.

Steps

Gather the decision context: what problem or question triggered this decision.
List all alternatives considered, including the status-quo option.
For each alternative, document pros, cons, risks, and estimated effort.
Identify stakeholder positions and any dissenting opinions.
State the chosen alternative and the primary rationale for selection.
Document expected consequences (positive and negative) of the decision.
Define revisit criteria — conditions under which this decision should be reconsidered.
Write the memo in the standard template and save to artifacts/decision-memos/.
Validate the artifact using ./tools/artifact/validate.sh.

Quality Checklist

Decision context is clearly stated and specific
At least two alternatives (including status-quo) are documented
Each alternative has pros, cons, and risk assessment
Stakeholder positions are captured accurately
Chosen alternative has explicit rationale
Consequences section covers both upside and downside
Revisit criteria are defined with measurable triggers
Artifact passes validation

このリポジトリの他の Skills

同じリポジトリ

setup

vibbs/company-os

Interactive setup wizard for Company OS. Configures company.config.yaml, generates .claude/settings.json with tech-stack-specific permissions, and scaffolds directories. Supports three modes — interactive wizard, express config block, or auto-extract from a URL/unstructured text.

2026-05-316

architecture-draft

vibbs/company-os

Produces RFC/ADR defining system boundaries, modules, data model, and integration points. Use when translating a PRD into technical design, making architectural decisions, or designing new system components.

2026-05-316

excalidraw

vibbs/company-os

Produces architecture diagrams, data flow diagrams, ERDs, and system overviews in Mermaid (inline) and Excalidraw JSON (standalone). Use when an RFC, threat model, or documentation needs visual diagrams.

2026-05-316

threat-modeling

vibbs/company-os

Performs data flow threat analysis with structured mitigations. Use when assessing security threats for new features, architecture changes, or compliance reviews.

2026-05-316

channel-playbook

vibbs/company-os

Creates platform-specific marketing playbooks for acquisition channels. Use when launching or optimizing a specific growth channel (e.g., LinkedIn, Twitter, email, Product Hunt).

2026-03-176

customer-conversations

vibbs/company-os

Prepares pre-call briefings, captures post-call debriefs, and routes insights to ICP refinement and PRD evidence. Stores conversation logs as CONV- artifacts in artifacts/decision-memos/.

2026-03-176

Decision Memo Writer

Reference

ID: S-ORG-02

Category: Orchestration

Inputs: decision context, alternatives, stakeholder positions

Outputs: decision memo artifact → artifacts/decision-memos/

Used by: Orchestrator Agent

Tool scripts: ./tools/artifact/validate.sh

Purpose

Procedure

ID Convention

Use the format DM-{NNN} for decision memo IDs (e.g., DM-001, DM-002). For specialized memos, use prefixes:

REVIEW- for review memos (e.g., REVIEW-WEEKLY-2026-03-01)

RETRO- for retrospective memos (e.g., RETRO-PRD-001)

GROWTH- for growth experiment memos (e.g., GROWTH-001)

CONV- for customer conversation logs (e.g., CONV-001)

Check artifacts/decision-memos/ for existing IDs to avoid collisions.

Steps

Gather the decision context: what problem or question triggered this decision.

List all alternatives considered, including the status-quo option.

For each alternative, document pros, cons, risks, and estimated effort.

Identify stakeholder positions and any dissenting opinions.

State the chosen alternative and the primary rationale for selection.

Document expected consequences (positive and negative) of the decision.

Define revisit criteria — conditions under which this decision should be reconsidered.

Write the memo in the standard template and save to artifacts/decision-memos/.

Validate the artifact using ./tools/artifact/validate.sh.

Quality Checklist

Decision context is clearly stated and specific

At least two alternatives (including status-quo) are documented

Each alternative has pros, cons, and risk assessment

Stakeholder positions are captured accurately

Chosen alternative has explicit rationale

Consequences section covers both upside and downside

Revisit criteria are defined with measurable triggers

Artifact passes validation

name	decision-memo-writer
description	Produces structured decision records with rationale, alternatives considered, and consequences. Use when recording non-trivial decisions that future team members need to understand.