Skip to content
Back to skills

Camp Workitems

ASecurity

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.

  • 60 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 6, 2026
ai-agentsgoshellbash

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add Obedience-Corp/festival --skill camp-workitems --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Camp Workitems?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Camp Workitems
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/obedience-corp-camp-workitems-festival/badge)](https://www.skillsdirectory.com/skills/obedience-corp-camp-workitems-festival)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: camp-workitems
description: 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.
version: "1.3.1"
author: Obedience Corp
license: Apache-2.0
metadata:
  hermes:
    tags:
      - camp
      - workitems
      - triage
      - planning
    category: camp
---

# Camp Workitems

Use `camp workitem` to find current camp work across intents, workflow
design/explore docs, festivals, and tracked workflow directories.

`camp workitem` is canonical. `camp wi` and `camp workitems` are aliases.

## Discover

Agents and scripts should prefer JSON:

```bash
camp workitem --json
camp workitem --json --type design --query auth
camp workitem --json --type intent --stage ready --limit 5
```

Use path output only when shell integration needs a destination:

```bash
camp workitem --print --type festival
```

Non-interactive use requires `--json` or `--print`.

Useful filters:

- `--type intent|design|explore|festival|<custom>`
- `--stage inbox|active|ready|planning`
- `--query <text>`
- `--limit <n>`

## Interactive

```bash
camp workitem
```

Use the TUI for human browsing, prioritization, and selection.

## Create Or Adopt

Use custom workitems for `workflow/<type>/<slug>` directories that should
appear in discovery.

```bash
camp workitem create <slug> --type feature --title "Human title"
camp workitem adopt workflow/feature/existing-dir --type feature --title "Human title"
```

Slug and type values must be path-safe: no `/`, `\`, whitespace, or control
characters; no leading `.` or `-`; max 80 characters.

## Avoid

- Running the interactive TUI from an agent session instead of using `--json`.
- Hand-writing tracking metadata for custom workitems. Use
  `camp workitem create` or `camp workitem adopt` so discovery state stays
  compatible.
- Editing `.campaign/settings/workitems.json` manually. It is tool-managed
  priority state, not the work-item source of truth.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.