Menu
SkillsMP has collected 14 skills from kalshamsi/fable-discipline-skills. Open a skill to review its source and details.
Showing 14 of 14 collected skills.
Before finalizing any plan, run a premortem — assume the plan has already failed, list the likeliest causes, and reshape the plan with mitigations before presenting it. Use this whenever producing something that will be executed later: project plans,…
Before executing any hard-to-reverse or destructive step, classify it as a one-way or two-way door; for one-way doors, substitute a reversible alternative or get explicit confirmation, and order work so mistakes can be undone. Use this whenever a plan or…
After two failed attempts at the same problem, stop and diagnose before trying again — never make a third attempt built on the same assumption. Use this whenever an approach has failed twice in a row, whenever you notice yourself making similar edits,…
Decide the bottom line before writing and put it in the first sentence, with only decision-relevant support after it. Use this whenever producing anything a reader will consume to decide or act — reports, emails, summaries, memos, recommendations, status…
Classify the user's intent before producing anything. When a message describes a problem, shares something that "seems off" or "doesn't look right", asks "what do you think", "does this make sense", "why is this happening", or thinks out loud without…
Before finalizing any analysis, recommendation, or decision made under incomplete information, surface the load-bearing assumptions, tag each as supported or unsupported by the given evidence, and stress-test the conclusion against the weakest one. Use this…
Attach explicit, evidence-tied confidence to every load-bearing judgment instead of asserting flatly or retreating into "it depends". Use this whenever the task involves a forecast, an estimate, a feasibility or go/no-go call, a deadline or risk question, or…
Audit the final section of a response before ending the turn - if it promises work, lists next steps the assistant could do itself, or defers with "let me know if...", do that work now instead of ending. Use this on every long, tedious, or multi-part task…
Audit every claim in a status update, completion report, handoff, or post-task summary against evidence from the actual work before sending it; state failures, skips, and partial results plainly and never claim more than the evidence shows. Use this whenever…
For any multi-step work, commit to an explicit ordered plan — steps, dependencies, and what done looks like — before producing the deliverable, then follow it and note deviations. Use this whenever a task has multiple parts, ordering constraints,…
Diagnose the underlying cause with evidence before proposing or applying any fix. Use this whenever anything is broken, failing, or degraded — bugs, errors, metric drops, missed deadlines, quality problems, process breakdowns, confusing behavior, or any "why…
Extract a request's explicit requirements into a checklist before drafting, then verify the draft against every item before delivering. Use this whenever a deliverable carries multiple explicit constraints — word or length limits, required sections or…
Deliver exactly what was asked and nothing more. Use this for any bounded change request — "fix X", "update Y", "only change Z", "just add one thing" — and for any edit to an existing document, plan, spreadsheet, message, or codebase, or any request with…
Check the referenced source and extract what it actually says before making any factual claim about it. Use this whenever a question concerns a specific document, dataset, file, report, spreadsheet, email thread, or other artifact; whenever source material is…