Hugo Nijhuis
d980a0d0bc
Update documentation and apply new frontmatter capabilities: Documentation: - Add user-invocable, context, agent, hooks fields to writing-skills.md - Add disallowedTools, permissionMode, hooks fields to writing-agents.md - Add model, context, hooks, allowed-tools fields to writing-commands.md - Document skill hot-reload, built-in agents, background execution Skills: - Add user-invocable: false to gitea (CLI reference) - Add user-invocable: false to repo-conventions (standards reference) Commands: - Add context: fork to heavy exploration commands (improve, plan-issues, create-repo, update-claude-md) - Add missing argument-hint to roadmap, manifesto, improve Agents: - Add disallowedTools: [Edit, Write] to code-reviewer for safety Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| View and manage the organization manifesto. Shows identity, personas, beliefs, and principles. |
Organization Manifesto
@~/.claude/skills/vision-management/SKILL.md
The manifesto defines the organization-level vision: who we are, who we serve, what we believe, and how we work. It is distinct from product-level vision (see /vision).
Process
-
Check for manifesto: Look for
manifesto.mdin the current repo root. -
If no manifesto exists:
- Ask if the user wants to create one
- Guide through defining:
- Who We Are: Organization identity
- Who We Serve: 2-4 specific personas with context and constraints
- What They're Trying to Achieve: Jobs to be done in their voice
- What We Believe: Core beliefs including stance on AI-augmented development
- Guiding Principles: Decision-making rules
- Non-Goals: What we explicitly don't do
- Create
manifesto.md
-
If manifesto exists:
- Display formatted summary of the manifesto
Output Format
When displaying an existing manifesto:
## Who We Are
[Identity summary from manifesto]
## Who We Serve
- **[Persona 1]**: [Brief description]
- **[Persona 2]**: [Brief description]
- **[Persona 3]**: [Brief description]
## What They're Trying to Achieve
- "[Job to be done 1]"
- "[Job to be done 2]"
- "[Job to be done 3]"
## What We Believe
[Summary of key beliefs - especially AI-augmented development stance]
## Guiding Principles
1. [Principle 1]
2. [Principle 2]
3. [Principle 3]
## Non-Goals
- [Non-goal 1]
- [Non-goal 2]
Guidelines
- The manifesto is the organization-level document - it applies across all products
- Update rarely - this is foundational identity, not tactical direction
- Product repos reference the manifesto but have their own
vision.md - Use
/visionfor product-level vision management