xiaohongshu
xiaohongshu
decision-charter
Create or update a Decision Interface Charter for recurring decisions
Full skill instructions
This skill supports three modes: Create, Update, and Find.
| 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
CREATE: Generate complete new charter using template below.
UPDATE:
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.
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)
Decision Interface Charters establish the "rules of engagement" for recurring decisions, ensuring consistent quality and accountability.
# 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]
xiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience