How do I install the Campaign Structure skill?

Run npx skillmds@latest add obedience-corp/campaign-structure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Campaign Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Campaign Structure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Campaign Structure free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Campaign Structure?

Obedience-Corp (@obedience-corp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Campaign Structure by obedience-corp

Name: Campaign Structure
Author: Obedience-Corp

Campaign Structure

Orient within a camp's directory structure. Use when deciding where work belongs (intents vs festivals vs design vs docs vs dungeon), especially when a task is not yet planned or folder ownership is unclear.

File contents

Camp Structure

A camp was previously called a campaign; the layout below is the same either way.

Placement Rules

Raw idea / bug / future work / quick capture: .campaign/intents/inbox/ (use camp intent add)
Enriching or preparing for execution: .campaign/intents/active/
Ready for structured work: .campaign/intents/ready/ → promote to festival
Structured multi-phase execution: festivals/
Internal design, architecture, or deep exploration: workflow/design/
User-facing documentation: docs/
Research, analysis, and exploration notes: workflow/explore/
Archive / defer / killed: .campaign/intents/dungeon/ or top-level dungeon/

Critical Distinctions

.campaign/intents/ (especially inbox/) is the primary capture surface for new ideas, bugs, and tasks.
workflow/design/ is for thoughtful internal design documents and specs.
festivals/ is for planned, phased execution (not raw ideas).
docs/ is user-facing; workflow/explore/ is internal.

Canonical reference: .campaign/intents/OBEY.md

Layout Snapshot (Current)

.campaign/
├── intents/          # Idea capture (inbox / active / ready / dungeon)
│   └── OBEY.md       # Authoritative intent guide
├── quests/           # Long-lived working contexts
└── skills/           # Camp-specific agent skills (loaded at runtime)

projects/             # Git submodules (the actual codebases)
workflow/
├── code_reviews/
├── pipelines/
├── design/           # Design documents & specs
└── explore/          # Historical research notes

festivals/            # Festival methodology (planning + active)
docs/                 # User-facing documentation
dungeon/              # Top-level archive

Common Mistakes

Putting raw ideas directly into festivals/ or workflow/design/ without going through intents first.
Treating docs/ as the place for internal specs (use workflow/design/ or .campaign/intents/).
Creating ad-hoc top-level directories instead of using the established taxonomy.
Forgetting that cgo i now navigates to .campaign/intents/.

---name: campaign-structuredescription: Orient within a camp's directory structure. Use when deciding where work belongs (intents vs festivals vs design vs docs vs dungeon), especially when a task is not yet planned or folder ownership is unclear.license: Apache-2.0---# Camp StructureA camp was previously called a campaign; the layout below is the same either way.## Placement Rules- Raw idea / bug / future work / quick capture: `.campaign/intents/inbox/` (use `camp intent add`)- Enriching or preparing for execution: `.campaign/intents/active/`- Ready for structured work: `.campaign/intents/ready/` → promote to festival- Structured multi-phase execution: `festivals/`- Internal design, architecture, or deep exploration: `workflow/design/`- User-facing documentation: `docs/`- Research, analysis, and exploration notes: `workflow/explore/`- Archive / defer / killed: `.campaign/intents/dungeon/` or top-level `dungeon/`## Critical Distinctions- `.campaign/intents/` (especially `inbox/`) is the primary capture surface for new ideas, bugs, and tasks.- `workflow/design/` is for thoughtful internal design documents and specs.- `festivals/` is for planned, phased execution (not raw ideas).- `docs/` is user-facing; `workflow/explore/` is internal.Canonical reference: `.campaign/intents/OBEY.md`## Layout Snapshot (Current)```text.campaign/├── intents/ # Idea capture (inbox / active / ready / dungeon)│ └── OBEY.md # Authoritative intent guide├── quests/ # Long-lived working contexts└── skills/ # Camp-specific agent skills (loaded at runtime)projects/ # Git submodules (the actual codebases)workflow/├── code_reviews/├── pipelines/├── design/ # Design documents & specs└── explore/ # Historical research notesfestivals/ # Festival methodology (planning + active)docs/ # User-facing documentationdungeon/ # Top-level archive```## Common Mistakes- Putting raw ideas directly into `festivals/` or `workflow/design/` without going through intents first.- Treating `docs/` as the place for internal specs (use `workflow/design/` or `.campaign/intents/`).- Creating ad-hoc top-level directories instead of using the established taxonomy.- Forgetting that `cgo i` now navigates to `.campaign/intents/`.

Frequently asked questions