Decision Interface Charter

VerifiedSafe

Creates, updates, or finds Decision Interface Charters to govern recurring decision-making. Establishes consistent rules of engagement for accountability and quality, especially useful in strategic decision governance.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#decision-charter#governance#recurring-decisions#decision-making

Recommended for

Automated summary

Creates or updates a Decision Interface Charter to govern recurring decisions.

Strengths

  • Establishes clear rules of engagement for recurring decisions
  • Ensures consistent quality and accountability
  • Supports create, update, and find modes
  • Provides a ready-to-use detailed template

Limitations

  • Requires pre-identified decision patterns
  • May be overkill for simple decisions
  • Does not solve the decision content itself
When to use it

When recurring decisions need consistent governance and documentation.

When not to use it

For one-off decisions or when speed is more important than structure.

Security analysis

Safe
Quality score88/100

This skill is a documentation template; no tools are called, no code is executed, and no destructive or data-exfiltrating actions are instructed.

No concerns found

How this analysis is made

Examples

Create charter for team prioritization
Create a Decision Interface Charter for team sprint prioritization decisions.
Update existing charter
Update the charter DIC-2025-003 to add a new escalation rule for budget overruns.
Find charters
Find all decision charters related to resource allocation.

name: decision-charter description: Create or update a Decision Interface Charter for recurring decisions argument-hint: [decision type] or [update path/to/charter.md]

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

| Signal | Mode | Confidence | |--------|------|------------| | "update", "revise", "modify" in input | UPDATE | 100% | | File path provided | UPDATE | 100% | | Charter ID mentioned (e.g., DIC-2026-001) | UPDATE | 100% | | "create", "new", "draft" in input | CREATE | 100% | | "find", "search", "list" | FIND | 100% | | "the charter", "our charter" | UPDATE | 85% | | Just decision type | CREATE | 60% |

Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate complete new charter using template below.

UPDATE:

  1. Check document registry first, then search user's structure
  2. Preserve charter ID and version history
  3. Update decision rules, criteria, or escalation paths
  4. Show diff summary

FIND: Check registry, then search user's folders for charters.


Create a Decision Interface Charter to govern how a recurring type of decision is made.

V2V Phase

Phase 2: Strategic Decisions - Decision charters establish governance for recurring decisions at any phase.

Prerequisites: Decision patterns identified, need for consistency recognized Outputs used by: All phases (provides decision governance)

Purpose

Decision Interface Charters establish the "rules of engagement" for recurring decisions, ensuring consistent quality and accountability.

Output Structure

# Decision Interface Charter: [Decision Type]

**Charter ID**: DIC-[YYYY]-[NNN]
**Version**: 1.0
**Last Updated**: [Date]
**Charter Owner**: [Role responsible for this charter]

## Decision Scope

**Decision Type**: [What recurring decision this governs]
**Examples**:
- [Example decision 1]
- [Example decision 2]
- [Example decision 3]

**Out of Scope**:
- [What this charter does NOT cover]

## Decision Classification

**Type**: Strategic / Portfolio / Execution
**Frequency**: [How often this decision typically occurs]
**Reversibility**: Low / Medium / High
**Impact**: Low / Medium / High

## Accountable Owner

**Role**: [Role, not person name]
**Authority**: [What they can decide unilaterally]
**Constraints**: [What requires escalation or consultation]

## Decision Forum & Cadence

**Forum**: [Where this is decided - e.g., "Weekly PLT meeting"]
**Cadence**: [When - e.g., "Thursdays 2pm"]
**Quorum**: [Who must be present]
**Duration**: [Expected time allocation]

## Required Inputs

| Role | Input Required | Format | Deadline |
|------|----------------|--------|----------|
| [Role 1] | [What they provide] | [Format] | [When before decision] |
| [Role 2] | [What they provide] | [Format] | [When before decision] |
| [Role 3] | [What they provide] | [Format] | [When before decision] |

## Decision Criteria

**Ready to Decide When:**
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

**Quality Threshold**: [What "good enough" looks like]

## Decision Rules

**How the decision is made:**
1. [Step 1]
2. [Step 2]
3. [Step 3]

**Tiebreaker**: [How to resolve if no clear answer]

## Escalation Rule

| Trigger | Escalate To | Timeline | Information Required |
|---------|-------------|----------|---------------------|
| [Trigger 1] | [Role] | [When] | [What to provide] |
| [Trigger 2] | [Role] | [When] | [What to provide] |

## Success Criteria

| Metric | Target | Timeframe | Measurement |
|--------|--------|-----------|-------------|
| Leading indicator | [Target] | T+2 weeks | [How measured] |
| Mid indicator | [Target] | T+6 weeks | [How measured] |
| Lagging indicator | [Target] | T+12 weeks | [How measured] |

## Re-decision Trigger

This decision should be revisited when:
- [Trigger 1]
- [Trigger 2]
- [Trigger 3]

## Communication Plan

| Audience | Channel | Timing | Owner |
|----------|---------|--------|-------|
| [Who needs to know] | [How] | [When] | [Who tells them] |

## Charter Review

**Review Frequency**: [How often to review this charter]
**Next Review**: [Date]
**Review Owner**: [Role]

Instructions

  1. Ask about the specific decision type if not clear
  2. Reference any governance documents provided via @file syntax
  3. Ensure accountable owner is a role, not a person
  4. Include specific escalation triggers
  5. Define measurable success criteria
  6. Save in charters/ folder
  7. Offer to create presentation version using /present

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/decision-interface-charter-mm78nod8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/decision-interface-charter-mm78nod8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/decision-interface-charter-mm78nod8/download' --output '.skill-downloads/decision-interface-charter-mm78nod8/SKILL.md.part' && mv '.skill-downloads/decision-interface-charter-mm78nod8/SKILL.md.part' '.skill-downloads/decision-interface-charter-mm78nod8/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/decision-interface-charter-mm78nod8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills