2.1K skills · sorted by relevance
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.
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.
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'.
The English summary is being prepared. Showing the original description.
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.
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.
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.
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.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Record software design decisions as numbered Markdown files, with context, rejected alternatives, benefits, drawbacks, and risks. Maintain an index and consult existing ADRs—architecture decision records—to explain why a framework, database, or design approach was chosen.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Two-layer memory for executive decisions, separating raw deliberation from approved decisions to prevent hallucinated consensus. Use when logging decisions, reviewing past decisions, or checking overdue action items.
The English summary is being prepared. Showing the original description.
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.