Claude Skills by jbkkz

Fold the user's answers into an existing Requivo session and refine the model one turn. Reasoning is this Claude session (no API key); the refined model is validated and applied, and any now-stale artifacts are reported. Use after /requivo:discover when the user has answered the open questions.

Produce the decision brief from a Requivo session's current understanding, using this Claude session for the judgment, and save it as a tracked document tied to the revision it was written from. Use when the questions have been worked through and the user needs something to review before estimating or committing to the scope.

Start a Requivo discovery from a client request. Reason with this Claude session (no API key), produce a validated requirements model, and ask only the high-information questions. Use when the user wants to turn a vague product request into a structured, traceable model.

Show what a change to a Requivo session touches — the decisions to re-validate and the artifacts that go stale — from the dependency DAG. Pure deterministic query, no reasoning, no API key. Use when the user asks "what does changing X affect?" or wants to know what to regenerate after a model change.

Generate a PRD from a Requivo session's model — a view of the model, with unknowns kept visible and open decisions left open — and save it as a tracked artifact. Use when the user wants a Product Requirements Document from a discovered model.

Show a Requivo session's readiness, blocking slots, current revision, and artifact freshness. Pure deterministic read — no reasoning, no API key. Use when the user asks where a session stands or what is still blocking it.