jbkkz
UserTurn a vague product request into a versioned requirements model: ask only the questions that change the solution, generate the brief and PRD from it, and compute exactly what a changed answer invalidates.
Categories
Indexed Skills (18)
requivo-discover
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.
answer
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.
discover
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.
brief
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.
prd
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.
status
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.
criteria
Draft test-ready acceptance criteria (a recette checklist) from a Requivo session's model, in this Claude session, and save them as a tracked artifact. Use when the user wants Given/When/Then scenarios a QA engineer can run and a client can sign off on.
epic
Turn a Requivo session's model into a delivery epic — a work breakdown a dev team can track and ship — in this Claude session, and save it as a tracked artifact. Use when the user wants an epic with trackable issues from the model.
estimate
Derive user stories and a day-based, uncertainty-aware effort estimate from a Requivo session's model, in this Claude session, and save both as tracked artifacts against one revision. Use when the user wants an effort estimate for the current scope.
release
Draft client-facing release notes from a Requivo session's model, in this Claude session, and save them as a tracked artifact. Use when the user wants an announcement a non-technical stakeholder can read to understand what they are getting.
stories
Decompose a Requivo session's model into implementable user stories, in this Claude session, and save them as a tracked artifact. Use when the user wants a delivery-planner's breakdown of the model into shippable slices.
docs
Show a menu of the seven documents a Requivo session's model can produce — decision brief, PRD, user stories, estimate, acceptance criteria, delivery epic, release notes — each with a one-line purpose and whether it is up to date, needs updating, or has not been generated. Generate the ones the user picks, one or several, reasoning in this Claude session. Use when the user wants a document but does not know its name, or wants to see what is fresh.
requivo-answer
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.
requivo-brief
Produce a solution assessment (brief) from a Requivo session's current model, using this Claude session for the judgment, and save it as a tracked artifact tied to the model revision. Use when discovery has converged and the user wants the senior-PM read of the requirements.
requivo-impact
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.
requivo-prd
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.
requivo-status
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.
impact
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.