discuss
discuss guides you through governance design conversations grounded in your repository's existing context. It helps identify constraints, compare design options, and produce durable artifacts like RFCs and ADRs that capture decisions and obligations without moving into implementation.
discuss explores governance design options and resolves ambiguity by drafting RFC or ADR artifacts without implementation.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
discuss explores governance design options and resolves ambiguity by drafting RFC or ADR artifacts without implementation. discuss guides you through governance design conversations grounded in your repository's existing context. It helps identify constraints, compare design options, and produce durable artifacts like RFCs and ADRs that capture decisions and obligations without moving into implementation.
Use it when
- discuss supports drafting ADR and RFC documents by walking you through governance design exploration.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
govctl-org/govctl/discuss · repository language: Rust
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is discuss and what governance tasks does it handle?
discuss is a governance design tool that guides you through structured conversations about architecture and policy decisions. It helps you explore RFC and ADR without coding, identify constraints from your repository's existing context, compare design options, and produce durable artifacts that capture decisions and obligations—all without moving into implementation.
How do I draft architecture decision records with discuss?
discuss supports drafting ADR and RFC documents by walking you through governance design exploration. It helps you analyze design trade-offs, establish decision rationale, and validate governance artifacts before lifecycle transitions. You can resolve design ambiguity governance by comparing options and documenting your reasoning without writing implementation code.
Can discuss help me explore design options and resolve ambiguity?
Yes. discuss is built to explore and discuss governance design options to resolve ambiguity at high priority. It grounds conversations in your repository's existing governance artifacts and constraints, then helps you analyze design trade-offs and establish clear decision rationale for each option you consider.
What kind of governance artifacts can discuss help me create?
discuss helps you draft RFC or ADR artifacts without implementing code. It supports governance artifact drafting, design rationale documentation, and governance design review processes. You can also validate governance artifacts before lifecycle transitions to ensure they meet your requirements.
Does discuss require me to write code or just discuss design?
discuss is purely a discussion and drafting tool—it produces durable artifacts like RFCs and ADRs that capture decisions and obligations without moving into implementation. You explore governance design options, compare trade-offs, and document rationale entirely through conversation and artifact creation, with no coding required.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Design Discussion
Understand $ARGUMENTS, relate it to existing governance, and produce only the
design artifacts justified by the discussion.
Operational Baseline
Discovery
Start from repository context rather than a blank design:
govctl status
govctl search <topic>
govctl rfc list
govctl adr list
Read relevant current artifacts with show; use --history only when prior
content matters. Use govctl <resource> --help for current authoring syntax. In
the govctl repository itself, invoke the development binary as
cargo run --quiet --.
Hard Stops
- This is a design workflow: do not implement code or create Work Items.
- Do not perform lifecycle or destructive artifact mutations here, including acceptance/rejection, phase or version changes, deprecation, supersession, and deletion.
- Do not issue raw VCS commands; use the
commitskill when drafts should be recorded. - RFCs own obligations, ADRs own design
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/discuss/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Explore and discuss governance design options to resolve ambiguity”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Decision Analysis exposes assumptions, failure paths, and success conditions for high-stakes design choices. It uses premortem and backcast reasoning to rank options against constraints, reversibility, and evidence quality, then returns a risk-calibrated recommendation. The skill routes obligations and rationale to their authoritative destinations—RFC, ADR, Work Item, or verification—rather than creating artifacts itself.
migrate helps you add govctl governance to an established project by examining existing evidence—documentation, code structure, VCS history, and configuration—to recover consequential decisions and specifications. It guides you through a discovery phase, presents candidates for backfill as Architecture Decision Records, RFCs, or Work Items, and executes only authorized changes in small coherent batches. The workflow preserves traceability, respects existing artifact state, and stops when evidence conflicts or authorization is unclear.
commit creates a coherent, single-outcome VCS change while enforcing governance rules and linking to active work items. It detects your repository type (Jujutsu or Git), validates against govctl policies, and ensures unrelated changes stay separate. The skill handles traceability, commit message formatting, and post-commit verification in one workflow.
ADR Writer guides you through documenting architectural decisions by establishing the problem context, weighing real alternatives, explaining why one direction won, and recording both benefits and costs. It enforces boundaries between decision rationale and product obligations, keeping ADRs focused on justification rather than execution or RFC-level commitments.
RFC Writer guides you through composing normative RFCs—product contracts with observable obligations, invariants, and compatibility rules. It enforces separation between specification prose and implementation details, ensures each clause is independently testable, and hands off lifecycle operations to dedicated governance tools. Use it to author the contract itself, not design rationale or execution scope.
gov delivers substantive code changes within your repository's governance framework, enforcing RFC and ADR authority while maintaining work-item traceability. It establishes current state, validates against normative specifications, and ensures completion evidence before closure.
More skills detach (MIT)