「decisions」の検索結果

Document development environment requirements for team consistency and AI agent understanding during PRD v0.6 Architecture. Triggers on requests to define environment setup, document tooling, create dev setup guide, or when user asks "what tools do I need?", "environment setup", "dev environment", "CLI requirements", "project setup", "onboarding setup". Consumes TECH- (stack selections), ARC- (architecture decisions). Outputs ENV- entries for development, CI/CD, and infrastructure environments. Feeds v0.7 Build Execution.

日本語の概要は準備中です。原文の説明を表示しています。

Capture durable, project-specific learnings from the work just done into the knowledge/ base — gotchas, implementation quirks, things looked up or web-searched, live-API behaviours, and design decisions (as ADRs). Use before opening a PR (it runs automatically in /deliver), or any time you've learned something worth remembering. Records only non-obvious, reusable facts; skips anything already in the repo, CLAUDE.md, or git history.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.

日本語の概要は準備中です。原文の説明を表示しています。

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, beat planning, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-motion`.

日本語の概要は準備中です。原文の説明を表示しています。

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.

日本語の概要は準備中です。原文の説明を表示しています。

Writes architecture decision records (ADRs) and keeps the rest of a project's documentation true after a change: README, reference comments on public interfaces and the changelog. Use when a user says "write an ADR", "record this decision", "document why we chose X", "set up a decision log", "supersede the old decision", "update the README", "add a changelog entry" or "document this API". Produces records in the Nygard or MADR format, a Keep a Changelog entry, and a script that checks the log for gaps and broken supersession links.

日本語の概要は準備中です。原文の説明を表示しています。

Guides a founder from real decisions to a short set of written company values that people can act on: collects incidents, tests each candidate value, writes it as a trade-off with behaviors and a story, and wires it into hiring, feedback and promotion. Use when someone asks to "define our company values", "write a values document", "our values are generic, fix them", "turn our values into interview questions", "what should our culture be before we hire", or wants to check whether the team lives the values it has. Produces VALUES.md, an evidence log and an interview kit.

日本語の概要は準備中です。原文の説明を表示しています。

Understand essential business finance — profit margins, unit economics, cash flow, LTV/CAC, and the 4 methods to increase revenue. Use when: analyzing business profitability, making pricing decisions, evaluating SaaS unit economics, financial planning.

日本語の概要は準備中です。原文の説明を表示しています。

Reconstructs the workflow behind a past artifact by querying local ax session, recall, and commit history data. Use when a user asks "what made X work", "how was Y shipped/built", "extract workflow from <date|sha>", "workflow around <topic>", "recipe for this feature", or similar. It finds the anchor session or commit, inspects ax sessions, ax recall, and ax sessions show, and returns an ordered read-only narrative with decisions and evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Master the AI tools that transform financial operations. From bookkeeping to forecasting, manage money smarter and make data-driven financial decisions. Use when "finance, accounting, budgeting, forecasting, FP&A, bookkeeping, expense management, finance, accounting, budgeting, forecasting, fpa, expenses" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in feature prioritization - the art and science of deciding what to build and in what order. Covers prioritization frameworks, roadmap planning, stakeholder management, and the trade-offs between different approaches. Knows that prioritization is about saying no, and how to make those decisions defensible. Use when "prioritization, roadmap, what to build, feature request, backlog, scope, trade-off, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when "keywords, file_patterns, code_patterns, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in course platform selection and implementation - comparing Teachable, Kajabi, Thinkific, and custom solutions. Covers LMS selection criteria, platform migrations, tech stack decisions, and building vs buying. Use when "course platform, lms, teachable, kajabi, thinkific, course hosting, learning management system, which platform, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Technical decision-making frameworks - trade-off evaluation, reversibility analysis, and second-order thinking for better engineering choicesUse when "should we, which is better, trade-off, decision, choose between, versus, pros and cons, what if we, is it worth, evaluate options, decisions, trade-offs, architecture, adr, reversibility, strategy, planning, risk" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in measuring what matters in communities. Covers health metrics, engagement analytics, sentiment analysis, cohort tracking, and reporting. Knows that good data drives good decisions, and bad metrics drive bad behavior. Use when "community metrics, community analytics, measure community, community health, engagement metrics, community reporting, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

The practice of collecting, analyzing, and acting on data to drive product decisions. Great analytics isn't about dashboards—it's about insights that lead to action. Every metric should answer a question that changes behavior. This skill covers event tracking, metrics design, dashboards, user behavior analysis, and data-driven decision making. The best analytics teams measure what matters, not what's easy to measure. Use when "analytics, metrics, tracking, dashboard, funnel, cohort, retention, events, KPI, measure, data, insights, conversion, engagement, analytics, metrics, data, dashboards, tracking, funnels, cohorts, KPIs, insights" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Researches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug.

日本語の概要は準備中です。原文の説明を表示しています。

Keeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Framework workflow skill. Use this skill when the user needs Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Framework workflow skill. Use this skill when the user needs Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。