discipline

Plugin discipline from marketplace melodic-software in melodic-software/claude-code-plugins. Commands read from the repo's manifest — today.

Skills (17)

• be-ambitious

  Raises one request before work starts: shows the original beside a version with a higher goal, deeper methods and wider range, fenced to a scope the user accepts, and waits. After work, deepens and redoes it with an outside check. Typed by the user who suspects they asked for, or got, less than they

• do-your-research

  Re-anchors research discipline: audits and corrects work and pending recommendations, or fans out to verify every session claim. Use when: 'do your research', 'you're guessing', 'cite that', 'stop assuming', 'evidence, not vibes', 'you skipped verification', 'that's training-data recall', 'research

• follow-our-standards

  Re-anchors to the organization's engineering standards, audits the work in flight against them, and corrects violations with doc citations. Use when: 'follow our standards', 'follow the standards', 're-anchor to standards', 'does this match our conventions', 'audit against standards', 'you're drifti

• hold-my-hand

  Standing posture for multi-step work: only the current phase (exact steps, expected output, common failure, who acts, advancing reply), later ones as a 'Phase 1 of 8' count. Use when: 'hold my hand', 'walk me through this', 'one step at a time', 'one phase at a time', 'don't show me the next step ye

• mind-your-maxims

  Re-anchor cooperative communication (Grice's maxims plus AI-augmented transparency): audit recent responses and artifacts for completeness (neither too little nor too much), relevance, clarity, and disclosed boundaries. Use when: 'mind your maxims', 'communication quality', 'answer what I asked', 'y

• pick-for-the-problem

  Re-anchors fitting a tool, library, framework, language, or approach to the problem, not habit, incumbency, or preconception; re-derives the choice. Use when: 'pick for the problem', 'right tool for the job', 'which library should we use', 'what framework', 'should we build this or use X', 'is this

• point-dont-copy

  Re-anchors pointer-over-copy discipline: audits the work in flight for copied content, internal-name coupling, and closed capability lists, and corrects by pointing at the living source. Use when: 'point don't copy', 'you copied that', 'don't duplicate the docs', 'cite instead of paste', 'link don't

• reason-dont-recite

  Re-anchors: inherited content is evidence of what is, never self-justifying authority; re-derives choices coasting on precedent. Use when: 'reason don't recite', 'why is it this way', 'challenge that convention', 'you're deferring to precedent', \"that's just how it's done\", 'question the inherited

• recheck-against-upstream

  Re-anchors that existing state (config, code, docs, infra) is not evidence of its own correctness, and audits it against CURRENT official upstream docs. Use when: 'recheck against upstream', 'check this against the docs', 'is our config still current', 'did upstream change', 'are we still doing this

• reuse-or-replace

  Re-anchors anti-fragmentation: given an established way, new work REUSES it or openly REPLACES it (migrate, record why), never a SILENT second way. Use when: 'reuse or replace', 'we already have a way of doing this', 'don't invent a second way', 'keep it one way', 'follow the existing pattern or rep

• script-the-deterministic-work

  Re-anchor: deterministic sub-work (counts, diffs, transforms, arithmetic) gets a script; reason over its output. Use when: 'script the deterministic work', 'you should have scripted that', 'don't eyeball that', 'you counted that by hand', 'compute that, don't estimate', 'diff it with a tool', 'stop

• scrutinize-dont-coast

  Re-anchor adversarial self-scrutiny: stop coasting on recent output, re-examine whether it is sound (not merely confident) in a fresh-context pass blind to its reasoning, and remediate with the user. Use when: 'scrutinize don't coast', 'wait, stop', 'are you sure about this', 'second-guess this', 'p

• setup

  Validate the discipline plugin's configuration (the posture-batch override, do-your-research's fan-out verification depth, lever_scope and docs/conventions/discipline.yaml), explain how to change the personal options through Claude Code's plugin configuration prompt, and write the repository file af

• sweep-all

  Batches this plugin's discipline correctors into ONE pass; needs fork subagents (`subagent_type: fork`), else (and at conversation start) reports only a posture digest and audits nothing. Use when: 'sweep all disciplines', 'ground ourselves', 're-anchor everything', 'run the whole re-anchor bundle',

• tighten-your-output

  Re-anchors terseness discipline (markdown in fewer words without semantic loss, code in fewer lines when readability holds), then audits the work in flight for avoidable verbosity and tightens it. Use when: 'tighten your output', 'tighten this', 'too verbose', 'say it in fewer words', 'this is bloat

• use-your-skills

  Re-anchors actually using the session's skills: maps the task to the listing, invokes the fitting skill instead of reinventing it, names skills when delegating, and audits for one that should have fired. Use when: 'use your skills', 'you have a skill for that', 'did you check your skills', 'there's

• wait-what

  The reader lost the thread of the previous reply. Explain it again, adding the context they lacked, in ASD-STE100 Simplified Technical English and the project's own domain terms. Type /discipline:wait-what the moment you notice you are skimming; only the reader knows when they stopped following.

Similar plugins