quality-strategy

Plugin quality-strategy from marketplace tollens in tollens-ai/quality-strategy-skills. Commands read from the repo's manifest — 2 days ago.

Skills (28)

• assess-quality-gaps

  Find out where a release stands against its quality priorities, or where one quality question stands, by investigating on the user's behalf in the ways planned with them. Use once there is a way of checking, to learn how good things are now, how sure anyone can be, what falls short, and which questi

• contradiction-check

  Find claims in quality documents, or a section, that cannot both be true. Use for a focused consistency check that tells contradictions apart from missing information, uncertainty and stakeholder disagreements.

• evaluation-strategy

  A deliberately light follow-up to /quality-strategy for the evaluation lane — ingest the release's quality strategy, filter for the ilities where better judging or better indication can make a dent (Unknowns nothing can judge yet, claims resting on signals that couldn't support them, "we wouldn't no

• operational-distillation

  Turn a complete-but-dense quality or test strategy into something operational — a 6–10 line TL;DR plus a one-page triage rubric (and an optional operator cheat sheet) placed at the top of the doc, so a returning reader re-orients in seconds instead of skimming hundreds of lines. Use from /quality-st

• oracle-adequacy

  Audit whether a quality strategy's actual-state assessment can be trusted — for each dimension, is there an adequate oracle to judge what level the project is actually at, and an adequate instrument to observe it? The explicit "how do we know?" (Q2) check that agents skip by deferring to whatever me

• plan-quality-measurement

  Agree how the release's priorities would be judged, before anything is measured, as checks that each answer one or more rows, or for one quality question. Use to work out what to observe and what result would show the bar is met, and to choose suitable ways of checking.

• plan-quality-work

  Choose and order the user's next actions on quality, from an assessment or a known concern - what they do about the gaps and how they find out what is open. Use to work out what to do about gaps, unclear expectations or missing evidence, and produce a plan of next actions or a clearer question.

• priority-analysis

  Compare and order an agreed set of options using the decision owner's criteria, stakeholders' views, evidence and constraints. Use for a careful comparison of options with the tradeoffs made explicit; to choose a priority's next actions within a strategy, use priority-deepdive instead.

• process-strategy

  A deliberately light follow-up to /quality-strategy for the rules-and-processes lane — ingest the release's quality strategy, filter for the ilities that rules, invariants, standards, or repeatable processes can make a dent on, then per ility discuss what you have, what could be improved, and what c

• progress-story

  Create a self-contained before-and-after visual from two identified versions of quality strategy records. Use when someone wants to see what changed and what the evidence supports, without mistaking changed wording, requirements, confidence or scope for a better product.

• quality-artefacts

  Turn a finished quality strategy into a shareable, glanceable visual artefact — a bespoke self-contained SVG or HTML file designed for a stated audience and purpose. Describe the view you want ("a tweetable summary of where quality stands", "a story of our quality year, told frame by frame", "a dash

• strategy-variants

  Derive audience-facing variants from a finished quality strategy — a distributable one-pager for the people the strategy names, and a client-safe ("polite") version that drops frank internal candor without lying. Use after /quality-strategy has produced and reviewed quality/strategy.md, when you nee

• test-strategy-review

  Audit a test strategy document. Asks "will carrying out these agreed moves move the quality strategy in the right direction with the right priority?" by forward-walking the moves as the primary lens, with mechanical checks as backstop. Use after /test-strategy completes, or to audit an existing qual

• test-strategy

  A deliberately light follow-up to /quality-strategy for the testing lane — ingest the release's quality strategy, filter for the ilities testing can make a dent on (where you don't know where you stand and investigating would tell you), then per ility discuss what testing you have, what could be imp

• tooling-adequacy

  Find out whether a quality question has a suitable way to observe the product (an instrument) and to judge what is seen (an oracle). Use when a proposed way of knowing needs a closer look, or on its own to examine test tooling and oracles.

• tooling-strategy

  Produce the strategy for the second quality question — "how do we know if what we have is good?" Gathers every place the strategy lanes could NOT answer that (risk-map Unknowns nothing can judge yet; build items agreed in /evaluation-strategy; /test-strategy moves blocked on instruments or oracles)

• connect-quality-strategy

  Write the quality strategy up as one document from the records, straight after the release priorities - an opening, then a section for each priority ending in its open questions and their next actions - then check it against its sources and give it to the user. Use after the priorities, again when t

• draft-strategy-steps

  Draft steps of a quality strategy without the user, for them to review later. Use when the user asks to skip ahead to a later step, or asks the agent to draft steps or stakeholders itself. Asks for the project context to be done with the user first.

• establish-project-context

  Find out or update the background that quality work needs, including the project's purpose, scope, how work gets done, releases, stakeholders, and how each stakeholder relates to the products, tools or other things involved. Use before other quality work needs that background, or when the purpose, r

• pre-read

  Read one or more software project repositories, without changing them, and write a digest with sources of what the files show - the major issues obvious from the code and architecture, what the tests cover and do not, a first reading of how friendly the codebase is to agents working on it, and what

• prioritise-release-quality

  Combine every stakeholder's view into one set of quality priorities for a release, with how much each matters and what is not a priority for it. Use once each stakeholder who matters has had their deepdive, or to revise or re-order the release's priorities.

• priority-deepdive

  Work one release priority further with the strategy owner, once the strategy is written up, so that someone can act on its section. Use for any priority they name or choose.

• quality-interview

  Hear what matters to someone about a software project's quality, and what worries them, in their own words before any structured strategy work, so the strategy does not miss it. Keeps their account in a transcript, topic records and a summary that later steps check the strategy against. Use when som

• quality-report

  Make something to show from quality strategy records, such as a striking, faithful visual to share, a page a reader can explore, a report for a particular reader, or an operational summary. It is the last step of a strategy, and can also be used on a focused or partial one whenever someone wants to

• quality-setup

  Agree once, for a project, where its quality documents are kept and who they are for, and save that so every later session finds it. Use before the first step of a quality strategy or interview on a project, or to change where its documents live.

• quality-strategy-review

  Review whether a quality strategy, or one context, stakeholder, priorities or priority-section document, supports the understanding, question or decision it is meant for. Use to review existing quality work on paper, at the scope it states.

• quality-strategy

  Find where a quality strategy stands and what to do next. Explains what a strategy is for, the steps and why they come in that order, and names the one step to run next. Use to start a strategy or to find your place in one.

• stakeholder-deepdive

  Record the user's understanding of one stakeholder or group for a release - who they are, what matters to them, how good it must be, what comes first for them - and the questions the user still has about them, saved as their profile. Use once for each stakeholder before the release priorities, or to

Similar plugins