make-no-mistakes-toolkit

Guided entry point for repo health when you don't know which audit you need. Use when the user asks "which audit", "where do I start", wants to check "repo health", or mentions "domain driven" design. Inspects the repo, asks a few plain-language questions, recommends which audit(s) to run (or the full ordered sweep), runs them via the audit-engine, and finishes with a premortem on the remediation plan. Best first command for a new repo.

Audit a repo for structural anti-patterns and repo health: schema drift, duplicated logical columns, multiple writers with no owner, and the broader six-family sweep. Use when the user asks to "audit" a repo, hunt for "drift" or an "anti-pattern", check "repo health", or run a named detector profile (e.g. schema-drift / SCH). Owns the full flow: preflight, scope, detect, verify, cure-map, emit (findings doc + OpenSpec change + Bilingual Linear issues + 4-cure scaffold proposals). Do NOT trigger for premortems, code review of a single PR, or generic status reports.

Reads spec files or SRD tasks and produces structured implementation briefs in the Bilingual Format (Human Layer + Agent Layer). Use when the user asks to "analyze this spec", "create an implementation brief", "process this SRD task", "what needs to be built from this spec", or wants to turn a spec document into actionable implementation steps. Supports OpenSpec, numbered steps, and SRD gap audit. Do NOT trigger for: issue analysis (use spike-recommend), code review, or status reports.

Cross-references open PRs across all repos in the current org with Linear issues, checks Greptile review scores, forces mergeable calculation, and generates an actionable report with merge/rebase/fix recommendations. Use when the user asks "show me open PRs", "what PRs need attention", "review PRs", "check Greptile scores", "what's ready to merge", or wants a comprehensive PR status overview. Do NOT trigger for: creating PRs, code review, or single PR inspection.

Detects when the user wants to work on a Linear issue, implement a feature, fix a bug, or start development work. Suggests the /make-no-mistakes:implement command. Triggers on: "implement", "work on issue", "start on", "pick up issue", "Linear issue", "build feature", "fix bug", "start coding", "work on <PREFIX>-NNN" or "implement <PREFIX>-NNN" for any Linear issue prefix (APP, BACK, SEC, MYTEAM, etc. — based on your workspace), "implement this", "let's build", "start implementing", "pick up this ticket", "work on this task", "execute this issue", "develop this feature", "ship this", pastes a Linear issue URL, or provides an issue ID. Does NOT trigger on: rebase, sync branches, standup, test execution, code review, general coding questions, or session management tasks.

Analyzes issues and produces structured bilingual implementation briefs (Human Layer + Agent Layer). Use when the user asks to "analyze this issue", "create an issue brief", "what does this Linear issue need", pastes a Linear issue URL, or wants to understand and plan work for an issue. By default, the brief is written back to the tracker (Linear / GitHub Issues / etc.) — not to a local file. Do NOT trigger for: general project management or status updates unrelated to a specific issue.

Applies MoSCoW (bucket) + RICE-adapted (intra-bucket ranking) to Linear issues of a product pillar, traceable to its PIBER+IDCF sub-spike and the latest vision audit. Use when the user asks to "prioritize issues", "priorizar el pillar", "aplicar MoSCoW", "rank the backlog", "RICE scoring", "/prioritize", or wants a data-backed decision on what to work on next within a pillar. Do NOT trigger for: generic backlog ranking without pillar context (use spike-recommend or implement-advisor instead), issue creation, or PR review.

Reviews active Linear issues with GitHub cross-referencing, activity insights, and actionable recommendations. Use when the user asks "what are my active issues", "review my Linear issues", "what's the status of my issues", "show me my backlog", "what issues need attention", or wants a comprehensive view of their Linear workspace. Do NOT trigger for: creating new issues, PR review, or code implementation.

Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: "premortem this", "premortem my", "run a premortem", "what could kill this", "future-proof this", "stress test this plan", "what am i missing here", "find the blind spots". STRONG TRIGGERS: "what could go wrong", "am i missing anything", "poke holes in this", "where will this break", "devil's advocate this". Do NOT trigger on simple feedback requests, factual questions, or LLM Council requests. DO trigger when someone has a plan or commitment where the cost of being wrong is high.

Detects when the user needs to sync branches after a release or rebase their work across multiple branches. Suggests the /make-no-mistakes:rebase command. Triggers on: "sync with release", "rebase all branches", "align with develop", "post-release sync", "branches are behind", "need to rebase everything", "team rebase", "release sync", "sync after merge to main". Does NOT trigger on: single-branch rebase ("rebase this branch"), git rebase interactive, cherry-pick, or simple merge operations.