12 skills · sorted by relevance
Record founder-approved decisions with chosen options, success measures, stop conditions, and dissent. Keep approved decisions separate from discussion transcripts so future advisory sessions use confirmed choices, with a review scheduled after 90 days.
Send a founder’s strategic question to the appropriate executive advisor by matching its wording and intent. Questions spanning several roles go to a boardroom discussion, while unclear questions receive an intake to clarify the issue.
Work through founder decisions with 13 executive-role agents and 21 slash commands. Use focused questions or multi-role discussions to clarify tradeoffs, record decisions, and turn the outcome into a 90-day action plan.
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.
Faithfully append a human modeler's choice and rationale to one canonical per-subquestion JSONL decision ledger. Use after a choice card is answered or when migrating legacy decision artifacts; never originate or improve the decision.
The English summary is being prepared. Showing the original description.
Turn meeting notes into an accountable register — extract decisions, actions and open questions, flag ownerless items, track follow-through. Use when commitments get dropped or a recurring meeting decides nothing.
The English summary is being prepared. Showing the original description.
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.
Print your own north-star row from your own record, and nothing else. Reads .claude/harness/decision-log.md, the canvas and the hook logs in this project; prints one line (decisions before the first source file, of which citing outside evidence, kills before code, sessions). Sends nothing anywhere. Opt-in; paste the line where you like or not at all.
The English summary is being prepared. Showing the original description.
Use when important product, technical, or founder decisions need to be captured as durable context with rationale, tradeoffs, and follow-up implications.
The English summary is being prepared. Showing the original description.
Record and track organizational decisions using the RAPID framework. Captures decision context, options analysis, RAPID roles, risk assessment, and communication plan. Use when making cross-functional decisions, documenting governance choices, or building an auditable decision trail.
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.
Capture the "why" behind technical choices to prevent architectural drift. Load when the user makes a major technical decision, chooses a library/framework, defines a system boundary, or changes a core architectural pattern. Also triggers on "record a decision", "write an ADR", "why did we do this", "document this architectural choice", or "architectural decision record". Supports `SYNTHESIS=true` mode for retrospective ADR backfill from observed repo state — used by `retroactive-project-setup` and any future backfill skill. Essential for long-term project maintainability and agent alignment.
The English summary is being prepared. Showing the original description.