productize-structured-decision-journals-from-decisions-and-context
Structured decision journals from decisions and context. Use when the user needs a product workflow for decision making related to structured decision journals from decisions and context. Trigger terms: pm, decision-making, journaling, forecasting, base-rates.
- License 许可
- MIT
- 最近更新
- 2026-08-07
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- productize-structured-decision-journals-from-decisions-and-context
- description
- Structured decision journals from decisions and context. Use when the user needs a product workflow for decision making related to structured decision journals from decisions and context. Trigger terms: pm, decision-making, journaling, forecasting, base-rates.
02 资源文件 1
- 参考文档agents/openai.yaml409 B
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly --> <!-- Regenerate: npm run skills:generate -->
Structured decision journals from decisions and context
Productize Preamble
Before producing the artifact, implementation step, or code change, classify the work:
- User/persona: founder, product leader, AI PM, AI builder, stakeholder, or mixed/unknown.
- Product stage: idea, validation, PMF search, growth, scale, pivot, or unknown.
- Artifact mode: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.
- Artifact format: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.
- Evidence standard: what is known, assumed, missing, and risky.
- Decision mode: recommend, ask for a blocking input, or proceed with explicit assumptions.
Operating rules:
- Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.
- Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.
- Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.
- Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.
- If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.
- Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.
- End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.
- Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.
- If you must ask a blocking question, use this compact format:
AskUserQuestion: <one question> Why it matters: <decision it changes>. - Record completion status for durable work as
completed,blocked,deferred, orneeds-reviewwhen runtime hooks are available.
Artifact format policy:
- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.
- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams/tables/comparisons/screenshots, the artifact is meant to be shared, or interaction/export controls would help the user stay in the loop.
- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.
- HTML artifacts must be local-first and portable: one file, embedded CSS/JS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.
- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy/export buttons when they improve review speed. Avoid decorative complexity that hides the decision.
- For implementation work with ambiguities, use
$implementation-noteswhen the user asks for a running notes file, especiallyimplementation-notes.htmlorimplementation-notes.md.
Runtime hooks, if available:
- Use
productize-workflow start "<user request>"at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract. - Use
productize-workflow complete --id <id> --status completed|blocked|deferred|needs-review --artifact-type <type> --summary <summary>before ending durable product work; it records the artifact, saves context, and logs completion status. - Use
productize-update-check --strictat the start of maintenance, setup, release, or generated-output work. - Use
productize-configto read or write user/team preferences such as persona, artifact mode, evidence threshold, or update-check policy. - Use
productize-session-logto record important workflow decisions. - Use
productize-artifact-logwhen a durable artifact is produced. - Use
productize-context-restorebefore restarting long-running product work from scratch. - Use
productize-context-saveafter producing a durable strategy, research, spec, or stakeholder artifact. - Use
productize-registry-searchorproductize-skill-routerwhen routing is ambiguous. - Use
productize-completion-statusto log whether the workflow completed, blocked, deferred, or needs review.
Telemetry standard:
- Keep telemetry local by default in
.productize/orPRODUCTIZE_STATE_DIR. - Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.
Current skill metadata:
- Skill:
structured-decision-journals-from-decisions-and-context - Lifecycle: Think
- Category: Decision Making
- Primary artifact: Decision journal with decision frame, alternatives, outcomes, probabilities, base rates, disconfirming evidence, bias checklist, quit conditions, and review plan
Use this skill to run the Productize prompt contract for Structured decision journals from decisions and context.
Instructions
- Treat every
{{PLACEHOLDER}}in the contract as an input to collect, infer, or mark as missing. - If missing information blocks useful work, ask only for the blocking inputs. If work can proceed, state assumptions explicitly.
- Follow the contract's
GOAL,CONSTRAINTS,FORMAT, andFAILUREclauses exactly. - Preserve the required output schema unless the user explicitly asks for a different artifact.
- Keep claims grounded in the provided inputs and disclose gaps.
Prompt Contract
INPUTS <provided_inputs>
- {{DECISION}}
- {{CONTEXT}} </provided_inputs>
GOAL Produce a high-quality deliverable for: "Structured decision journals from decisions and context". Success metric:
- Produces a complete decision journal with all required sections filled from provided context.
- Probability estimates are coherent and sum to 100%.
- Quit conditions are measurable and actionable.
- Output follows the required structure exactly.
CONSTRAINTS
- Use only
{{DECISION}}and{{CONTEXT}}; if information is missing, state assumptions explicitly. - Separate facts, assumptions, missing evidence, and risky leaps before forecasting.
- Generate 3-5 expected outcomes spanning best-case to worst-case and covering short-term and long-term effects.
- Provide one probability for each expected outcome; probabilities must total exactly 100%.
- Include the strongest alternative option considered, not only the chosen path.
- Provide 3-5 key assumptions that materially affect outcome validity.
- Provide relevant base rates/statistics tied to this decision type; if unavailable, provide directional proxies and label as assumptions.
- Include disconfirming evidence that would weaken the decision.
- Include a bias checklist for anchoring, availability, confirmation, sunk cost, status quo, optimism, and loss/risk aversion.
- Provide 2-3 measurable quit conditions with clear trigger thresholds.
- Provide a decision review date and owner.
- Keep
<actual_results>intentionally blank for future updates.
FORMAT Return exactly this structure:
<decision_journal> <decision_frame> [Decision, owner, date, context, and chosen option] </decision_frame>
<facts_assumptions_missing_risky> Known facts: Assumptions: Missing evidence: Risky leaps: </facts_assumptions_missing_risky>
<alternatives_considered>
- [Chosen option]
- [Strongest alternative]
- [Optional additional alternative] </alternatives_considered>
<expected_outcomes>
- [Outcome]
- [Outcome]
- [Outcome] [Optional 4th and 5th outcome] </expected_outcomes>
<probability_estimates>
- [Outcome 1] - [X%]
- [Outcome 2] - [Y%]
- [Outcome 3] - [Z%] [Optional 4th and 5th probability] Total: 100% </probability_estimates>
<key_assumptions>
- [Assumption]
- [Assumption]
- [Assumption] [Optional 4th and 5th assumption] </key_assumptions>
<base_rates>
- [Base rate/statistic + source context or rationale]
- [Base rate/statistic + source context or rationale] [Optional additional base rates] </base_rates>
<disconfirming_evidence>
- [Evidence that would weaken or reverse the decision]
- [Evidence to seek before/after deciding] </disconfirming_evidence>
<bias_checklist> Anchoring: Availability: Confirmation: Sunk cost / escalation: Status quo: Optimism: Loss or risk aversion: </bias_checklist>
<quit_conditions>
- [Condition + measurable threshold]
- [Condition + measurable threshold] [Optional 3rd condition] </quit_conditions>
<actual_results> </actual_results>
<review_plan> Owner: Review date: What would change the decision: </review_plan> </decision_journal>
FAILURE
- Any required section in
FORMATis missing, malformed, or incomplete. - Fewer than 3 or more than 5 expected outcomes.
- Probability estimates do not map to outcomes or do not total 100%.
- Fewer than 3 key assumptions or fewer than 2 quit conditions.
- Quit conditions are not measurable.
- No strongest alternative, disconfirming evidence, bias checklist, review owner, or review date.
- Claims are generic or not grounded in provided inputs.
<actual_results>is pre-filled with outcome claims.- Assumptions are used but not explicitly stated.
04 同仓库更多 Skills
workflow-memory
Maintains workflow-scoped task memory for Productize runs using .productize/tasks/<name>/memory/ files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.
review-round
Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.
productize
Productize root skill for building, shipping, operating, and growing AI products inside a coding harness. Routes work across thesis framing, discovery, research, positioning, finance, decision making, requirements, design, metrics, AI-builder execution, code implementation, verification, stakeholder narratives, growth, launch, operation, and learning workflows. Use when the user wants to build a product from zero, improve an existing product, or needs product work that spans multiple lifecycle stages before code, launch, operation, or growth execution.
productize-wwas
Why-What-Acceptance. Use when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.
productize-writing-plans
Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.
productize-write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea into a structured document, scoping goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into phases.