← all publishers

Obedience-Corp

@obedience-corp source repo

Report this profile Claim this profile

• 12 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Camp Projects · obedience-corp

   Manage a camp's projects. Use when committing inside `projects/*`, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.
   0
   installs
2. ▌
   Fest Planning · obedience-corp

   Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states.
   0
   installs
3. ▌
   Camp Workitems · obedience-corp

   Find, filter, choose, create, or adopt camp work items with `camp workitem`, `camp wi`, or `camp workitems`. Use when a user wants current active work across intents, designs, explore notes, festivals, or tracked workflow directories; when agents need safe `camp workitem --json` output; or when creating/adopting tracked workflow folders.
   0
   installs
4. ▌
   Cross Campaign · obedience-corp

   Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.
   0
   installs
5. ▌
   Fest Execution · obedience-corp

   Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
   0
   installs
6. ▌
   Camp Navigation · obedience-corp

   Navigate a camp with `cgo` and `camp go`. Use when you need to move between projects/festivals/workflow directories, switch context quickly, or resolve script-safe paths with `camp go --print`.
   0
   installs
7. ▌
   Campaign Commit · obedience-corp

   Choose the correct commit command in a camp, also called a campaign. Use when you are about to commit and need to select `camp commit`, `camp p commit`, `fest commit`, or intentional root pointer sync via `camp refs-sync`.
   0
   installs
8. ▌
   Festival Intake · obedience-corp

   Route work that is too large for a single chat into a structured plan. Use when the user describes a multi-step build, a migration, a rewrite, an audit, a refactor across many files, or a research question with several threads. Use when a goal would otherwise need step-by-step supervision across more than one session. Also use when the user says "plan this", "where do I start", "help me build X", "this is a big one", or hands over a spec, a ticket, or a document and asks what to do with it.
   0
   installs
9. ▌
   Fest Methodology · obedience-corp

   Use when the user mentions festivals, the fest CLI, phases, sequences, or tasks, or when working inside a `festivals/` directory. Provides the core Festival methodology model so Claude understands the planning system.
   0
   installs
10. ▌
    Campaign Structure · obedience-corp

    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.
    0
    installs
11. ▌
    Campaign Workflows · obedience-corp

    Manage a camp's intents, dungeons, and workflow collections with `camp`. Use when capturing ideas, promoting intents to festivals, archiving work, or moving workflow items between statuses.
    0
    installs
12. ▌
    Fest Standalone Workflows · obedience-corp

    Create and run lightweight standalone `WORKFLOW.md` loops with `fest create workflow`, `fest next`, and `fest workflow advance`. Use when a user wants step-by-step workflow guidance inside any ordinary directory, explore/design work item, project folder, or thin-start workflow.
    0
    installs