Decision Extractor
Extract decisions from notes and maintain accurate project Decision Logs
What You Can Do
This skill systematically searches your vault and Slack across specified time ranges to identify decisions using natural language patterns. It extracts decision context—including rationale, participants, dates, and sources—then matches decisions to projects and identifies gaps in your Decision Logs. You get a curated list of decisions that should be documented, reducing the risk of losing critical project decisions in the noise of daily communications.
Features
searches weekly reports, meeting notes, and Slack messages across custom time ranges (this week, last 2 weeks, this month)
recognizes 15+ decision patterns including 'decided to,' 'agreed on,' 'approved,' 'moving forward with,' and deprioritization language
captures the decision itself, date, participants, project/topic, rationale, and source (vault file or Slack channel/thread)
automatically identifies which project each decision relates to and checks existing Decision Logs for duplicates
surfaces decisions made in Slack threads that may not have been captured in formal notes
narrow scans by project name or time range to focus on what matters most
flags decisions missing from project Decision Logs so you can add them before they're forgotten
tracks whether decisions came from vault files or Slack, preserving the audit trail
Example Output
Scanning vault and Slack (last 2 weeks, Project: Customer Portal)...
Found 4 decisions:
-
Decision: Move to PostgreSQL for data layer
- Date: 2024-01-15
- People: Sarah (tech lead), Mike (backend)
- Rationale: Better scalability for growth projections; existing team expertise
- Source: Weekly Report — 2024-01-15 Engineering Sync
- Status: ✅ Logged in Decision Log
-
Decision: Delay Q1 mobile launch to Q2
- Date: 2024-01-18
- People: Product team, exec sponsor
- Rationale: Resource constraints; prioritizing web stability
- Source: Slack — #customer-portal (thread: Jan 18, 2:45 PM)
- Status: ⚠️ NOT in Decision Log — add now?
-
Decision: Approve vendor contract with AuthPlus
- Date: 2024-01-16
- Rationale: Cost savings 30%; meets compliance requirements
- Source: Weekly Report — 2024-01-16 Procurement Notes
- Status: ✅ Logged in Decision Log
-
Decision: We won't pursue SMS notifications MVP
- Date: 2024-01-17
- Rationale: Low user demand from surveys; feature creep risk
- Source: Slack — #product-strategy (Jan 17, 10:22 AM)
- Status: ⚠️ NOT in Decision Log — add now?
What's Included
- SKILL.md: core instruction file with arguments, scanning logic, decision language patterns, and project matching rules
- Decision Extraction Checklist: markdown template to manually verify found decisions before logging
- Decision Log Template: markdown structure for documenting decisions (date, people, rationale, status, source)
- Time Range Reference: quick guide for setting scan parameters (this week, last 2 weeks, this month)
- Slack Integration Setup: brief reference for enabling the Slack MCP tool if needed
Who It's For
- Project managers — keep Decision Logs current without manually hunting through notes and Slack
- Engineering/product leads — ensure architectural and product decisions are formally documented and discoverable
- Operations teams — maintain governance audit trails by capturing all decisions in centralized logs
- Scrum/Agile masters — track sprint and roadmap decisions for retrospectives and planning
- Compliance officers — preserve decision rationale and participants for audit and risk management
Best For
- Weekly decision capture and logging across multiple communication channels
- Identifying decisions buried in Slack threads that haven't made it to formal documentation
- Closing gaps in project Decision Logs during retros or audits
- Creating an audit trail linking decisions to their rationale and participants
- Bulk scanning of archived notes or reports to surface missed decisions
You might also like
You can systematically synthesize signals from multiple fashion sources—runway shows, street style, consumer behavior, fabric innovations, and cultural movements—to identify which silhouette changes will gain traction in upcoming seasons. This skill accelerates the analytical process by organizing observations into structured forecasting frameworks that help you spot inflection points where silhouette preferences shift, enabling you to develop product roadmaps and communicate trend reasoning to design teams and merchandisers with data-backed justification.
by er1chu
You can rapidly identify emerging color trends by processing competitive intelligence, social media sentiment, runway analysis, and cultural indicators into structured forecasts. Claude helps you validate pattern strength across multiple data sources and build defensible color recommendations backed by cultural movements, consumer psychology, and market performance—enabling you to justify palette choices to executives and design teams with 6-18 month lead time.
by er1chu
You can systematically identify which teams must complete work before others can start, pinpoint the critical path that determines your actual end date, and create sequencing plans that prevent bottlenecks. This skill reveals invisible dependencies—like why marketing can't plan assets until engineering confirms the launch date—and helps you communicate realistic timelines to stakeholders based on actual workflow constraints, not optimistic assumptions.
by jzocb
You can systematically plan and execute complex projects by creating a persistent file-based working memory that survives context resets. Claude maintains three core files (task_plan.md for phases, findings.md for discoveries, progress.md for session logs) that keep your project organized, prevent information loss, and enable automatic recovery after session breaks or /clear commands.
by liangdabiao
This skill generates detailed, role-specific launch readiness checklists that scan your codebase, content systems, and infrastructure for common launch blockers. It automatically detects code quality issues (TODOs, debug statements, placeholders), validates build health, checks content calendars and store readiness, and creates structured sign-off documents for each department. You can run it in dry-run mode to preview the checklist or execute it to generate official pre-launch documentation with approval tracking.
by donchitosCreate detailed exit plans tailored to your business, including financial valuations, timeline development, tax optimization, and stakeholder communication strategies. Claude analyzes your business situation and generates customized exit roadmaps covering sale preparation, acquisition readiness, or succession planning with risk mitigation frameworks and buyer positioning tactics.
by er1chu
You can deconstruct supplier sustainability claims, identify hidden environmental costs across a material's full lifecycle, and compare alternatives based on equivalent functionality rather than isolated metrics. This skill helps you quantify trade-offs between sustainability dimensions—durability vs. water use, certifications vs. actual impact—so you can justify material choices to design teams, purchasing departments, and consumers with evidence-based reasoning.
by er1chu
You can transform disparate consumer signals—purchase behavior, social engagement, demographic shifts, and psychological motivations—into coherent trend narratives with actionable forecasting insights. This skill focuses on the why behind behavior rather than surface aesthetics, helping you identify inflection points where consumer preferences are shifting, validate collection strategy against actual psychology, and build predictive consumer profiles for 6-18 month forecasting horizons.
by er1chu