メニュー
Manage persona themes - list available themes, show current/specific theme details, set active theme, create themes, and run the interactive theme maker wizard.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | theme |
| description | Manage persona themes - list available themes, show current/specific theme details, set active theme, create themes, and run the interactive theme maker wizard. |
| args | [list|show|set|create|maker] [options] |
Manage persona themes for agent characters.
| Command | CLI | Purpose |
|---|---|---|
/theme | pf theme show | Show current theme |
/theme list | pf theme list | List all available themes |
/theme show [name] | pf theme show [name] [--full] | Show theme details |
/theme set <name> | pf theme set <name> [--dry-run] | Set active theme |
/theme create <name> | pf theme create <name> [--base X] [--user] [--dry-run] | Create from base theme |
/theme maker | (interactive wizard) | AI-driven theme creation |
Refresh the current agent persona:
pf agent start "sm"
Adopt the new character immediately.
| Location | Purpose |
|---|---|
pennyfarthing-dist/personas/themes/ | Built-in themes (96+) |
.claude/pennyfarthing/themes/ | Project-level custom themes |
~/.claude/pennyfarthing/themes/ | User-level custom themes |
.pennyfarthing/config.local.yaml | Active theme selection |
Detailed options and behavior: usage.md Practical examples and theme maker guide: examples.md
Interactive playtest — full-stack (UI + Playwright + UX Designer) or headless (API-only + Python driver). Coordinates cross-workspace bug reporting via ping-pong file with FIXER.
LLM cost and cache forensics — reconcile server-log narrator costs against the Anthropic Admin API, attribute per-model spend, detect dead caching and invisible callers. Use when analyzing API costs, auditing cache efficiency, or when the Console bill doesn't match expectations.
Create epic or story context documents. Reads sprint YAML for epic/story data, reads context-schema.yaml for required sections, populates templates, and writes output to sprint/context/. Epic context is a single-agent operation (no tandem). Story context uses PM + tandem partner for domain-specific observations.
Jira CLI commands for sprint management. Use when viewing, assigning, or updating Jira issues from the command line.
Sprint status, backlog, and story management for Pennyfarthing. Use when checking current sprint status, finding available stories, reviewing backlog, or understanding story context and history. IMPORTANT: Always use `pf sprint` CLI commands - never manually edit sprint YAML.
List available workflows, show current workflow details, and switch workflows mid-session. Use when checking available workflow types (TDD, trivial, agent-docs), viewing current workflow phase, switching to a different workflow pattern, or managing BikeLane stepped workflows.