Initializes complete governance framework including constitution, roadmap, and templates. Use when setting up new projects or establishing governance in existing projects lacking systematic documentation.
Creates foundational governance documents including constitution, roadmap, and process templates for new or existing projects.
npx claudepluginhub bacchus-labs/wranglerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/detailed-guide.mdtemplates/DEFINITION_OF_DONE.mdtemplates/SECURITY_CHECKLIST.mdtemplates/TESTING.mdThis skill creates the three-tier governance hierarchy:
CONSTITUTION.md) - Immutable design principlesROADMAP.md + ROADMAP_NEXT_STEPS.md) - Strategic + tactical plans1. Detect Project Structure
Use Bash to check current state:
# Check for git repository
git rev-parse --show-toplevel
# Check for existing wrangler workspace
ls -la .wrangler/ 2>/dev/null || echo "No .wrangler directory"
# Check for existing governance docs
[ -f .wrangler/CONSTITUTION.md ] && echo "Constitution exists" || echo "No defining-constitution"
[ -f .wrangler/ROADMAP.md ] && echo "Roadmap exists" || echo "No roadmap"
2. Ask User for Project Context
Use AskUserQuestion to gather essential information:
AskUserQuestion({
questions: [
{
question: "What is the core mission of this project in one sentence?",
header: "Mission",
options: [
{ label: "I'll type it myself", description: "Provide custom mission statement" }
],
multiSelect: false
},
{
question: "What stage is this project currently in?",
header: "Stage",
options: [
{ label: "Brand new", description: "Just starting, no code yet" },
{ label: "Early development", description: "Some code exists, still evolving" },
{ label: "Active development", description: "Established codebase, ongoing features" },
{ label: "Mature", description: "Stable codebase, maintenance mode" }
],
multiSelect: false
},
{
question: "Do you have existing design principles or guidelines?",
header: "Principles",
options: [
{ label: "Yes, documented", description: "Have written principles already" },
{ label: "Yes, informal", description: "Have ideas but not written down" },
{ label: "No, need help", description: "Want to create them now" }
],
multiSelect: false
}
]
})
3. Create Directory Structure
Ensure all required directories exist:
# Create directories if they don't exist
mkdir -p .wrangler
mkdir -p .wrangler/docs
mkdir -p .wrangler/plans
# Note: .wrangler/issues and .wrangler/specifications are created by session hooks
4. Create Process Documentation
Create standard process documentation files from skill templates:
# Copy TESTING.md from skill template
cp skills/initializing-governance/templates/TESTING.md .wrangler/TESTING.md
TESTING.md will be populated later by setting-up-git-hooks with actual test commands.
Initial state should have placeholder status:
{{STATUS_PLACEHOLDER}} with: **Status:** Not configured yet{{TEST_COMMAND}} and other placeholders as-isNote on Templates: Issue and specification templates live in their respective skills:
skills/creating-issues/templates/TASK_ISSUE_TEMPLATE.mdskills/writing-specifications/templates/SPECIFICATION_TEMPLATE.mdskills/initializing-governance/templates/SECURITY_CHECKLIST.mdskills/initializing-governance/templates/DEFINITION_OF_DONE.mdThese are referenced directly from skills, not copied to .wrangler/templates/.
5. Set Up Git Hooks (Automatic)
After governance files are created, automatically set up git hooks:
# Invoke setting-up-git-hooks skill
Skill: setting-up-git-hooks
This will:
.wrangler/TESTING.md (created in previous step).wrangler/config/hooks-config.json with configuration.git/hooks/ directoryUsers can reconfigure later with /wrangler:updating-git-hooks command.
If user has existing principles: Use the defining-constitution skill (invoke with Skill tool) to help them refine and formalize.
If user needs help creating principles: Guide them through brainstorming process:
1. Identify Core Values
Ask these questions (one at a time, discussion-style):
2. Convert Values to Principles
For each core value, help user formulate as concrete principle:
Template:
### [Principle Number]: [Principle Name]
**Principle**: [One-sentence statement of the principle]
**In Practice**:
- [Specific application 1]
- [Specific application 2]
- [Specific application 3]
**Anti-patterns** (What NOT to do):
- ❌ [Anti-pattern 1 with explanation]
- ❌ [Anti-pattern 2 with explanation]
**Examples**:
- ✅ **Good**: [Concrete example showing principle in action]
- ❌ **Bad**: [Concrete example violating principle]
3. Write Constitution File
Use the template from skills/defining-defining-constitution/templates/_CONSTITUTION.md:
# Copy template (if not using the skill to generate it)
cp /path/to/wrangler/skills/defining-defining-constitution/templates/_CONSTITUTION.md .wrangler/CONSTITUTION.md
Then use Edit tool to fill in:
1. Gather Roadmap Information
Ask user about phases and goals:
AskUserQuestion({
questions: [
{
question: "How many major phases do you envision for this project?",
header: "Phases",
options: [
{ label: "1-2 phases", description: "Small project, focused scope" },
{ label: "3-4 phases", description: "Medium project, several major milestones" },
{ label: "5+ phases", description: "Large project, long-term vision" }
],
multiSelect: false
}
]
})
2. For Each Phase, Gather Details
For first phase (most important):
For subsequent phases (can be less detailed):
3. Write Roadmap File
Use template from skills/validating-roadmaps/templates/_ROADMAP.md:
# Copy template (if not using the skill to generate it)
cp /path/to/wrangler/skills/validating-roadmaps/templates/_ROADMAP.md .wrangler/ROADMAP.md
Fill in with Edit tool:
4. Write Next Steps File
Use template from skills/validating-roadmaps/templates/_ROADMAP__NEXT_STEPS.md:
# Copy template (if not using the skill to generate it)
cp /path/to/wrangler/skills/validating-roadmaps/templates/_ROADMAP__NEXT_STEPS.md .wrangler/ROADMAP_NEXT_STEPS.md
Initial file should reflect current state:
1. Create Issues README
Create a minimal README with status metrics using template from skills/initializing-governance/templates/issues-README.md.
Use Edit tool to:
issues_list to get counts)2. Create Specifications README
Create a minimal README with status metrics using template from skills/initializing-governance/templates/specifications-README.md.
Use Edit tool to:
Note: Templates remain in their skill directories and are referenced directly:
skills/creating-issues/templates/TASK_ISSUE_TEMPLATE.mdskills/writing-specifications/templates/SPECIFICATION_TEMPLATE.mdNo copying to .wrangler/templates/ is needed. Skills reference templates from their own directories.
1. Update Project CLAUDE.md
If CLAUDE.md exists in project root, add governance section:
## Project Governance
This project uses a three-tier governance framework:
### Tier 1: Constitution (Immutable Principles)
**File**: `.wrangler/CONSTITUTION.md`
Supreme law of the project. All features and decisions must align with constitutional principles.
**Read this first** before working on any feature.
### Tier 2: Strategic Roadmap
**File**: `.wrangler/ROADMAP.md`
Multi-phase strategic plan showing project direction and feature phasing.
### Tier 3: Tactical Execution
**File**: `.wrangler/ROADMAP_NEXT_STEPS.md`
Granular tracking of implementation status with % completion metrics.
### Governance Workflow
Before implementing any feature:
1. Check constitutional alignment
2. Verify roadmap phase
3. Create/update specification
4. Break into tracked issues
5. Follow TDD implementation
6. Update progress in NEXT_STEPS
**Critical**: Use the `checking-constitutional-alignment` skill before starting new features.
2. Verify All Files Created
Run verification:
# List all governance files
echo "=== Governance Files ==="
ls -lh .wrangler/CONSTITUTION.md
ls -lh .wrangler/ROADMAP.md
ls -lh .wrangler/ROADMAP_NEXT_STEPS.md
ls -lh .wrangler/specifications/README.md
ls -lh .wrangler/issues/README.md
echo ""
echo "=== Directory Structure ==="
tree -L 2 .wrangler/
3. Create Welcome Issue
Use issues_create to create first issue explaining governance:
issues_create({
title: "Welcome to Project Governance Framework",
description: `## Governance Framework Initialized
This project now has a complete governance framework to ensure alignment between AI assistant and human partner.
### Key Documents
**Constitution** (\`.wrangler/CONSTITUTION.md\`)
- Immutable design principles
- Decision framework
- Amendment process
**Roadmap** (\`.wrangler/ROADMAP.md\`)
- Strategic multi-phase plan
- Feature phasing
- Success metrics
**Next Steps** (\`.wrangler/ROADMAP_NEXT_STEPS.md\`)
- Tactical execution tracker
- % completion metrics
- Prioritized work items
### Quick Start
1. Read the Constitution first
2. Review the Roadmap to understand phases
3. Check Next Steps for current priorities
4. Use MCP tools or skills to create issues/specs
### Next Actions
- [ ] Read CONSTITUTION.md thoroughly
- [ ] Review ROADMAP.md phases
- [ ] Identify first features to implementing-issue
- [ ] Create specifications for Phase 1 features
- [ ] Begin implementation following governance
### Skills Available
- \`checking-constitutional-alignment\` - Verify feature alignment
- \`defining-constitution\` - Refine principles and clarity
- \`verifying-governance\` - Check governance integrity
- \`refreshing-metrics\` - Update status metrics
Close this issue once you've reviewed all governance documents.
`,
type: "issue",
status: "open",
priority: "high",
labels: ["governance", "onboarding"],
project: "Governance Framework"
})
Provide Summary to User
Create summary message:
## Governance Framework Initialized
Your project now has a complete governance system ensuring we stay aligned on:
- Design principles (Constitution)
- Strategic direction (Roadmap)
- Tactical execution (Next Steps)
### Files Created
**Core Governance** (in `.wrangler/`):
- `CONSTITUTION.md` - [X] principles ratified
- `ROADMAP.md` - [Y] phases planned
- `ROADMAP_NEXT_STEPS.md` - Execution tracker
**Process Documentation** (in `.wrangler/`):
- `issues/README.md` - Issue management guide
- `specifications/README.md` - Specification guide
- `TESTING.md` - Test documentation (created here, populated by setting-up-git-hooks)
**Git Hooks** (always enabled):
- `.wrangler/config/hooks-config.json` - Hook configuration
- `.git/hooks/pre-commit` - Pre-commit hook
- `.git/hooks/pre-push` - Pre-push hook
### Next Steps
1. **Review Constitution**: Read `.wrangler/CONSTITUTION.md`
- Verify principles match your vision
- Use `defining-constitution` skill if refinement needed
2. **Review Roadmap**: Read `.wrangler/ROADMAP.md`
- Confirm phases and timelines
- Adjust priorities if needed
3. **Start Implementation**:
- Create specifications for Phase 1 features
- Use `writing-plans` skill to break into tasks
- Follow governance workflow for all features
### Governance Workflow
Feature Request ↓ Constitutional Check (use checking-constitutional-alignment skill) ↓ (if aligned) Specification (create with constitutional alignment section) ↓ Implementation Plan (use writing-plans skill) ↓
For detailed information, see:
references/detailed-guide.md - Complete workflow details, examples, and troubleshooting