Results for “decisions”

Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles). Handles creating new context documents, loading existing ones, and enriching them with new decisions. Use when starting a new feature, resuming work, making technical decisions, resolving questions, or when context needs to persist across sessions. Use this skill whenever the user mentions 'load context', 'update context', 'context doc', 'decisions', 'continue where we left off', 'what did we decide', or 'capture this decision'.

The English summary is being prepared. Showing the original description.

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

The English summary is being prepared. Showing the original description.

Update a product spec from a meeting transcript — extract decisions, open questions, spec changes, and flowchart updates. Use this skill when: - A meeting discussed changes to a product spec and you need to update the local .md + wiki page - The user shares a meeting URL or transcript ID and says "update the spec" - The user says "what needs to change in the spec from this meeting" - After processing a meeting, when decisions affect a spec's content (not just action items) Trigger phrases: "update spec from meeting", "what changed in the spec", "meeting to spec", "sync meeting decisions to spec", "add meeting decisions to spec"

The English summary is being prepared. Showing the original description.

Maintain clear business definitions and relationships in an existing glossary or CONTEXT.md. Flag unresolved meanings and refer lasting design choices to the existing architecture decision record workflow, keeping terminology separate from decision rationale and task status.

• Document business terms that need repeated explanation
• Clarify terms with multiple meanings
• Track domain interpretations awaiting confirmation

Turn product requests and planning documents into a concrete development plan. Document business rules, data ownership, service interfaces, and unresolved decisions so teams can see what must be settled before implementation begins.

• Turning a product requirements document into development requirements
• Aligning requirements for a feature spanning multiple services
• Documenting assumptions that repeatedly surface in reviews

Support product returns from eligibility checks and inspection to refunds and decisions about resale, repair, or disposal. The skill also provides frameworks for reviewing fraud indicators, handling warranty claims, and recovering costs from suppliers.

• Checking return eligibility and refund options
• Grading returned goods and choosing their next destination
• Reviewing suspicious return patterns

Turn meeting notes or transcripts into sourced decisions and action items with owners and deadlines. Check existing tasks for duplicates, then draft minutes, tickets, and follow-up messages while keeping missing details and unresolved conflicts visible.

• Extract action items from meeting notes
• Clarify decisions, owners, and missing deadlines
• Reconcile meeting commitments with existing tasks

Document why software decisions were made, which alternatives were considered, and what trade-offs remain. Create architecture decision records, README guidance, API documentation, and changelogs that help future contributors and AI agents understand the project.

• Recording design decisions and rejected alternatives
• Documenting public API changes
• Updating README setup instructions

Turn bundled Paperclip issues, comments, and documents into readable wiki updates covering project purpose, current progress, decisions, risks, and next actions, while preserving existing knowledge and citing the supporting activity.

• Summarizing recent project activity in a wiki
• Building wiki pages from historical project activity
• Recording decisions and their supporting evidence

Search persistent claude-mem memories to recover past decisions, solutions, and work history. Review compact search results, surrounding context, and selected details, or let the tool handle these steps automatically for a clear query.

• Recall decisions from earlier sessions
• Find solutions to previously resolved problems
• Review work history before a handoff

Coordinate decisions across multiple AI agents by synchronizing shared memory, combining knowledge, and weighing input by expertise. The skill also guides workload distribution, conflict handling, and recording decisions with their rationale.

• Combine agent opinions into a shared decision
• Synchronize knowledge across agents
• Redistribute work when an agent is overloaded

Revise an existing OpenSpec change plan and reconcile related planning documents. Incorporate new decisions, identify contradictions or gaps, and apply proposed document edits after confirmation, while leaving implementation code untouched.

• Incorporating new decisions into an existing change plan
• Checking planning documents for contradictions
• Reconciling related documents after an edit

Work through project decisions one question at a time, with a recommendation and brief reasoning. Record each settled answer immediately in project documentation, keeping unresolved questions visible and documents marked as drafts until explicitly accepted.

• Clarify goals and boundaries before implementation
• Record decisions as an interview progresses
• Preserve decisions when discussions are interrupted

Review Zoom meetings, calls, recordings, and transcripts to catch up on discussions and extract decisions, action items, and owners. Use Zoom's official connections to manage meetings and access supported chat, document, task, and whiteboard features.

• Catch up on a missed meeting from recordings or transcripts
• Extract decisions, action items, and owners
• Create, update, or delete Zoom meetings

Search and read Slack messages, channels, and threads to catch up on team discussions and decisions. Using the installed CLI and Slack’s official MCP server, it also supports channel posts and replies, with approval required for changes.

• Catch up on team discussions
• Find messages about past decisions
• Post updates to a channel

Organize treatment decisions already supplied and verified by authorized licensed professionals into local JSON documents. Check document structure, source references, declared review status, and supplied dates to support documentation handoffs without making clinical decisions.

• Organize verified clinician-authored treatment records
• Check source references and missing documentation fields
• List checkpoint dates already supplied by clinicians

Retrieve relevant Hindsight memories before planning or answering a request. Searches the agent’s own and shared memory stores, plus other relevant stores when needed, to bring past decisions, user preferences, and project context into the task.

• Checking past decisions before planning work
• Answering with previously recorded user preferences
• Finding context saved by other Bots or AI tools

Find context from past coding sessions in Hindsight long-term memory. Reuse memories already loaded for the session, search for missing details, and reason over accumulated records when answering questions about decisions, project context, or preferences.

• Revisit the reasons behind past implementation decisions
• Recover project context discussed in earlier sessions
• Check previously discussed preferences

Use Hindsight to recall past context, save reusable facts, and reason across accumulated memories. Supports continuity between conversations by preserving preferences, project decisions, and lessons learned, while helping explain the reasoning behind earlier choices.

• Resuming earlier work with relevant context
• Saving lasting preferences and project decisions
• Reviewing the reasons behind past decisions

Make system architecture decisions by clarifying requirements and constraints, comparing benefits and drawbacks, and considering simpler alternatives. Record the reasoning in ADRs, architecture decision records, so significant choices and their rationale are documented.

• Clarifying requirements before system design
• Comparing architecture patterns
• Documenting decisions and rationale in ADRs

Document major technical choices as Architecture Decision Records, or ADRs. Capture the context, alternatives, reasons, and consequences, then organize related records and track whether decisions are proposed, accepted, retired, or replaced.

• Recording reasons for choosing a framework or database
• Comparing design options and their trade-offs
• Sharing past decisions with new team members

Provides persistent project memory for AI agents through a local MCP server, a tool interface for agents. Stores and searches architecture decisions and implementation patterns, syncs with project documentation, and includes a dashboard for viewing memory usage.

• Save architecture decisions for later reference
• Search previously recorded implementation patterns
• Retrieve design notes by key

Give an agent rules for consulting long-term memory before work and saving decisions, corrections, and failures afterwards. It helps carry preferences and project conventions across sessions while preserving dated history and making conflicting memories visible.

• Carry preferences and project conventions across sessions
• Record user corrections for future tasks
• Preserve the history of changed decisions

Retrieve earlier decisions, preferences, and saved resources from OpenViking across sessions. Store durable information, import documents or repositories, and manage deletion, with guidance on how project memory is shared between directories and repository clones.

• Recall decisions from earlier sessions
• Save preferences and lasting decisions
• Import files, URLs, or Git repositories for later use