'decisions' 검색 결과

Keeps board meeting transcripts separate from founder-approved decisions, with owners, deadlines, and action items. Supports decision searches, overdue reviews, and conflict checks so later meetings can refer to approved outcomes without treating rejected proposals as agreements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording approved decisions after a board meeting
• Finding past decisions by topic or owner
• Reviewing upcoming and overdue action items

Route business questions to relevant executive advisor roles, coordinate discussions across multiple functions, and combine their findings into clear agreements, disagreements, and action items. Record decisions and flag approved decisions that are due for review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing fundraising with spending cuts
• Reviewing decisions across several business functions
• Clarifying conflicting advisor opinions

Trace changes in a game design document to related architecture decision records, which explain technical choices. Compare their assumptions with the revised design, report which decisions need review, and guide updates to decisions and requirement links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking architecture impact after changing game design
• Finding technical decisions based on outdated requirements
• Choosing whether to keep, revise, or replace a decision

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Document major technical decisions with their context, alternatives, reasoning, and consequences. The skill provides Architecture Decision Record templates and maintenance practices so teams can review past choices, track replacements, and explain decisions to new members.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording reasons for technology choices
• Comparing design options and trade-offs
• Explaining past decisions to new team members

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update Composio documentation content and changelogs
• Revise Fumadocs settings and documentation automation prompts
• Record or update documentation decisions

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Locate team files across separate working directories
• Record decisions that affect other agents
• Request input from another specialist

Work through sixteen open questions in four rounds to clarify major product decisions, risky changes, or large refactors. The agent adapts later questions to earlier answers, then turns your decisions into a step-by-step implementation plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying decisions before a major product change
• Planning a large refactor
• Deciding rollout order for a risky change

Review important choices the agent made during the current work and identify those it remains unsure about. It considers overlooked alternatives and returns a concise list in plain English when explicitly requested by name.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing uncertain choices during ongoing work
• Checking for alternatives that were overlooked
• Finding decisions that need further discussion

Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기술이나 설계를 선택한 이유를 배경, 대안, 영향과 함께 Markdown으로 기록합니다. 일련번호와 색인으로 정리하고 기존 기록에서 과거 판단의 근거도 찾습니다.

• 프레임워크나 데이터베이스 선택 이유 기록
• 설계 대안과 장단점 정리
• 과거 기술 결정의 근거 확인

Help agents continue work in projects using Superself. Read current goals and decisions, attach work to tracked units, record progress with supporting evidence, and preserve confirmed decisions so later sessions can resume with context.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resume work using context from a previous session
• Track work units and evidence of progress
• Record confirmed decisions and their reasons

Design meeting schedules, weekly metric reports, and quarterly planning for growing companies. Clarify who makes decisions, assign owners to priorities, and structure written updates so teams can coordinate work and reserve meetings for issues needing discussion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Redesign meetings that fail to produce decisions
• Standardize weekly business metric reports
• Align quarterly priorities and resources across teams

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying the destination of an early idea
• Mapping decisions and their dependencies
• Resuming unresolved decisions across sessions

Search past conversations to recover decisions, discussions, and context across sessions. Find related ideas by meaning, match exact terms, or locate code identifiers, with options to search only user or assistant messages through local AI Maestro tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recalling decisions before resuming work
• Finding discussions with different wording
• Looking up conversations about a function or class

Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritize technical debt fixes by impact and effort
• Plan engineering hiring, timing, and budget
• Compare building internally with buying a service

Examine strategic decisions through a structured meeting of AI agents representing executive roles. Gather independent recommendations, challenge assumptions, summarize disagreements, and record approved decisions with action owners and deadlines after the founder reviews the proposal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluate market expansion from several executive perspectives
• Compare views on product direction or pricing
• Review hiring plans and organizational choices

Turn conversations and notes into organized Notion pages for decisions, guides, FAQs, and team knowledge. Create or update pages with summaries, source links, tags, and owners, then connect them to related documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record meeting decisions and their rationale
• Turn work notes into step-by-step guides
• Build FAQs from recurring conversations

Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find game requirements without architecture decisions
• Check for conflicts between architecture decisions
• Review compatibility with the pinned engine version

Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

Turn conversations and notes into organized Notion pages for decisions, guides, FAQs, and team knowledge. Create or update pages with summaries, source links, tags, and owners, then connect them to related documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record meeting decisions and their rationale
• Turn work notes into step-by-step guides
• Build FAQs from recurring conversations

Document how a research or coding session evolved after the work is complete. The skill extracts decisions, experiments, failed approaches, and claims into ara/ files, distinguishing user statements from AI suggestions and actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record the reasons behind research decisions
• Preserve failed experiments and their lessons
• Distinguish user decisions from AI suggestions