ReddRadar
Topic: flow
14 skills in this topic.
-
adr-writer
Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives
govctl-org/govctl 102
-
commit
Commit changes with govctl integration — check work item status, update journal or notes, and run govctl check
govctl-org/govctl 102
-
decision-analysis
Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off
govctl-org/govctl 102
-
discuss
Facilitate design discussion — research context, clarify requirements, draft RFC/ADR
govctl-org/govctl 102
-
gov
Execute governed implementation workflow with work items, RFC/ADR checks, phase gates, testing, and closure. Use when: (1) User invokes /gov, (2) A non-trivial change needs work item tracking, (3) Implementation may require RFC/ADR handling
govctl-org/govctl 102
-
guard-writer
Write well-structured Verification Guards. Use when: (1) Creating a new guard, (2) Editing guard check commands or patterns, (3) User mentions guard, verification, or check
govctl-org/govctl 102
-
init
Set up govctl in the current project. Installs the binary if missing, initializes governance structure.
govctl-org/govctl 102
-
migrate
Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield
govctl-org/govctl 102
-
quick
Execute the fast path for trivial changes with minimal governance ceremony. Use when: (1) User invokes /quick, (2) Change is doc-only or non-behavioral, (3) No RFC or ADR work is needed
govctl-org/govctl 102
-
rfc-writer
Write well-structured RFCs with normative clauses. Use when: (1) Creating a new RFC, (2) Adding or editing RFC clauses, (3) User mentions RFC, specification, or normative requirements
govctl-org/govctl 102
-
spec
Maintain governance artifacts without implementation work. Use when: (1) Accepting or refining ADRs, (2) Clarifying or amending RFCs without code changes, (3) Governance-only docs/check/render updates
govctl-org/govctl 102
-
wi-writer
Write well-structured work items with proper acceptance criteria. Use when: (1) Creating work items, (2) Adding acceptance criteria, (3) User mentions work item, task, WI, or ticket
govctl-org/govctl 102
-
thrivve-mc-how-many
Thrivve Partners Monte Carlo simulation to forecast story/task completion based on historical throughput. Use when the user asks "how many stories/tasks will be completed by [date]" with historical daily throughput data. Requires at least 10 days of throughput history and a future target date. Provides probabilistic forecasts at specified confidence levels (default 85%).
Thrivve-Partners/Claude-Skills-Forecasting 1
-
thrivve-mc-when
Thrivve Partners Monte Carlo simulation to forecast completion date based on remaining work and historical throughput. Use when the user asks "when will I complete [N] stories/tasks" with historical daily throughput data. Requires at least 10 days of throughput history, a count of remaining items, and optional confidence level (default 85%).
Thrivve-Partners/Claude-Skills-Forecasting 1