Loading...
Loading...
Found 38 Skills
Framework for structured product decision-making. Use when facing complex tradeoffs, aligning stakeholders, documenting decisions, or choosing between multiple valid approaches.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project
Evaluate options for a specific design decision node and recommend one with explicit trade-offs. Use when the design already exposes a concrete choice such as architecture style, state management approach, auth model, storage pattern, sync strategy, multi-agent coordination model, language or runtime, UI framework, data-layer library, or tooling selection. Trigger when the user needs structured comparison and recommendation for a bounded design decision. Do not use for broad design discovery, full-system decomposition, or final readiness review.
Ask and record decisions item by item regarding substantive unresolved user trade-offs in planning, product specifications, design, technical solutions, implementation, or release. Applicable to scope, priorities, trade-offs, risks, acceptance, dependencies, visual direction, or release authorization that cannot be closed from code, configurations, authoritative artifacts, or deterministic execution; it is not automatically triggered by new phases or new modules.
Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
Gather phase context through adaptive questioning before planning, clarifying implementation decisions, or exploring gray areas for a phase. Triggers include "discuss phase", "clarify phase", "gather context", "what are the gray areas", and "phase discussion".
Create structured technology trade-off analysis documents with scored comparison matrices. Use this skill whenever the user wants to compare technologies, evaluate architectural options, analyze build-vs-buy decisions, assess migration strategies, or produce any decision document that compares multiple approaches across weighted dimensions. Triggers on: 'trade-off analysis', 'tradeoff', 'comparison matrix', 'evaluate options', 'which technology should we use', 'compare approaches', 'pros and cons of', 'build vs buy', 'migration analysis', 'consolidation analysis', 'technology selection'. Also use when the user has completed technical research and wants to structure findings into a decision document.
Reaching shared understanding of what one Epic covers — inherit, interview at altitude, then recommend splitting it into thin children or specifying it. The what-step of Archie's planning phase.
Byzantine consensus voting for multi-agent decision making. Implements voting protocols, conflict resolution, and agreement algorithms for reaching consensus among multiple agents.
Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.
Use when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
Generate decision memos and product launch documents in Amazon's narrative style. Two modes: `memo` produces a 6-page narrative memo (Introduction, Goals, Tenets, State of Business, Lessons Learned, Strategic Priorities + unlimited appendix); `prfaq` produces a Press Release + External FAQ + Internal FAQ for product launches (work backwards from launch). Enforces Strunk's prose rules (active voice, concrete language, omit needless words, no qualifiers, parallel construction, topic-sentence paragraphs, no overstatement) and Anthropic's removability discipline at the line level. Use when: 'six pager', '6-pager', 'amazon memo', 'narrative memo', 'PRFAQ', 'press release', 'work backwards', 'decision memo', 'strategy doc', 'launch document', 'silent read doc', before any decision big enough to warrant the week-long writing process.