decision-moment-skill
Map and optimize decision moments across Awareness, Consideration, Conversion, and Retention, then attach specific assets, visuals, and automations to each stage. Use when designing funnels, campaigns, or retention systems.
Best use case
decision-moment-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Map and optimize decision moments across Awareness, Consideration, Conversion, and Retention, then attach specific assets, visuals, and automations to each stage. Use when designing funnels, campaigns, or retention systems.
Teams using decision-moment-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/decision-moment-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How decision-moment-skill Compares
| Feature / Agent | decision-moment-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Map and optimize decision moments across Awareness, Consideration, Conversion, and Retention, then attach specific assets, visuals, and automations to each stage. Use when designing funnels, campaigns, or retention systems.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Decision Moment Skill
## Purpose
Turn raw offers and services into structured decision-moment maps that tell us exactly:
- **Where** a prospect is in their journey
- **What** they need to see/feel/understand next
- **Which** asset (page, email, video, social post) should be delivered
## Outputs
For each client/campaign:
1. **Journey Map**
- Awareness → Problem Aware → Solution Aware → Provider Aware → Purchase → Retention
2. **Decision Moments**
- Each moment contains:
- Problem statement
- Blocking objection(s)
- Required proof
- Recommended asset type
- Link to asset in `social_assets` or page route
3. **Execution Map**
- Which channel carries which moment (email, ad, social, landing page)
## Data Structures (DB)
- `decision_moment_maps` table to hold the overall map
- `decision_assets` table to join moments to specific assets
## When to Use
- After Social Playbook creation
- When designing onboarding journeys
- When improving conversion on an existing flow
## Constraints
- Always align with the No-Bluff protocol and verified value propositions.
## Decision Moment Framework
### Stage 1: Awareness
- "I have a problem but don't know what to call it"
- Asset types: Educational content, social posts, blog articles
- Goal: Get attention, define the problem
### Stage 2: Consideration
- "I know the problem, exploring solutions"
- Asset types: Comparison guides, case studies, how-to videos
- Goal: Position as the best solution
### Stage 3: Conversion
- "Ready to buy, need final push"
- Asset types: Demos, trials, testimonials, pricing pages
- Goal: Remove final objections, close deal
### Stage 4: Retention
- "Customer, keep them happy and growing"
- Asset types: Onboarding, tutorials, upsells, check-ins
- Goal: Maximize lifetime valueRelated Skills
create-architectural-decision-record
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
decision-logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
decisions
Load past architectural decisions. Use when making new decisions to ensure consistency.
technical-decision-record
Use when making technical decisions, choosing technologies, or documenting architectural choices. Creates ADRs (Architecture Decision Records).
decision-action
Use when the user needs to choose, prioritize, or make a go/no-go decision among options.
architecture-decision-record
Use this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Helps teams maintain architectural memory and rationale for backend systems, API designs, database choices, and infrastructure decisions.
architecture-decision-records
在Claude Code会话期间,将做出的架构决策捕获为结构化的架构决策记录(ADR)。自动检测决策时刻,记录上下文、考虑的替代方案和理由。维护一个ADR日志,以便未来的开发人员理解代码库为何以当前方式构建。
Clinical Decision Support Documents
## Description
Daily Logs
Record the user's daily activities, progress, decisions, and learnings in a structured, chronological format.
Socratic Method: The Dialectic Engine
This skill transforms Claude into a Socratic agent — a cognitive partner who guides
Sokratische Methode: Die Dialektik-Maschine
Dieser Skill verwandelt Claude in einen sokratischen Agenten — einen kognitiven Partner, der Nutzende durch systematisches Fragen zur Wissensentdeckung führt, anstatt direkt zu instruieren.
College Football Data (CFB)
Before writing queries, consult `references/api-reference.md` for endpoints, conference IDs, team IDs, and data shapes.