Results for “decisions”

Use `analysis-agent` for release decisions, `task-agent` for delivery artifacts, or `review-agent` for readiness on deployment, migration, rollback, or production risk. Skip local work with no release decision.

Generates comprehensive questions about decisions before implementing. Explores requirements, constraints, success criteria, edge cases, and hidden assumptions in a SINGLE comprehensive prompt. Use when starting any significant work to surface unknowns early.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Synthesize the current conversation and codebase context into a Product Requirements Document and publish it to the project's issue tracker.

Diagnoses Qdrant capacity needs and guides horizontal scaling decisions, including node count, shard count, replication factor, and resharding trade-offs.

Optimizes long-running agent sessions with structured context compression, summarization, and durable handoff summaries that preserve decisions, files, risks, and next actions.

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Guides individuals through legal cases by clarifying the type of proceeding, preserving evidence, tracking deadlines, and partnering effectively with attorneys to make informed decisions.

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.

Record decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.

P10 CTO mode — define strategic direction, design org topology, manage P9 teams. Use when user says 'CTO模式', 'P10', '战略规划', '架构委员会', or when facing cross-team architectural decisions. Produces: strategic input templates + org design.

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

Encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

Audits hidden assumptions in decisions by classifying them, ranking by fragility and impact, and rebuilding conclusions from verified premises. Auto-detects Chinese or English input.

P10 CTO mode — define strategic direction, design org topology, manage P9 teams. Use when user says 'CTO模式', 'P10', '战略规划', '架构委员会', or when facing cross-team architectural decisions. Produces: strategic input templates + org design.

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

Use when evaluating potential risks before making decisions, starting initiatives, or implementing changes. This skill provides a structured risk assessment framework for identifying, analyzing, and responding to risks across all domains.

Use this skill when the user is designing any visual system, UI, graphic, layout, brand asset, or interface and needs structured, high-quality, communication-first design decisions across typography, layout, color, imagery, and UX.

Extract project vision and decisions from a user through iterative Q&A, then convert them into clear repo documentation (README, ADRs, lessons). Use when user asks to document ideas in their head.

Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.

Proceed through ordinary ambiguity by making reasonable assumptions, keeping momentum, validating as you go, and ending with a clear recap of decisions, changes, verification, and residual risk.

Convene a four-voice council of advisors to surface structured disagreement and tradeoffs for ambiguous decisions, go/no-go calls, and multi-path choices.

Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value to make data-driven build/don't-build decisions.

Audits colour decisions on a screen for contrast ratios, palette coherence, semantic meaning, and accessibility, flagging deviations and recommending specific corrections.

Provides multi-agent creative collaboration for filmmaking, integrating the styles of 31 renowned directors to assist with scriptwriting, visual style design, and narrative decisions.

Guides data analysis, EDA, and ML tasks by teaching, diagnosing MCPs, and deciding with the user, offering multiple options and documenting decisions.

Guides strategic product decisions, pricing, backlog prioritization, and trend intelligence, routing tasks to specialized sub-skills.

Provides a strategic advisory persona based on A.G. Lafley, applying the Strategy Choice Cascade and consumer-centric frameworks to business decisions.

Adopts the voice and reasoning methods of Aristotle to analyze problems, guide decisions, and improve communication through first principles, categorical thinking, and balanced moderation.

Structures an Architecture Decision Record (ADR) to capture context, decision, and consequences of significant architectural choices, ensuring decisions are documented with sufficient detail for future teams.

AI product architect guiding PRD-equivalent planning, architecture, and delivery planning decisions. Use when the user asks to talk to Dumbledore, requests the AI architect, or needs structured planning for an AI product.

Expert financial analyst specializing in financial modeling, forecasting, scenario analysis, and data-driven decision support. Transforms raw financial data into actionable business intelligence that drives strategic planning, investment decisions, and operational optimization.

Structures user research — planning sessions, synthesizing findings, and translating insights into product decisions. Use when planning user interviews, analyzing research data, creating personas or journey maps, or turning qualitative feedback into structured recommendations.

Use when creating, maintaining, or reviewing records of actions, decisions, changes, and events for compliance, accountability, and investigation purposes. This skill provides procedures for managing audit trails across all agent activities.

Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions.

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.