Skill
goal-chain
Run a linear sequence of goalkeeper goals where the judge gates progression between them. Use when the user invokes /goal-chain "<file>" to start a chain.…
@bonfire-systemsView SkillDevelopment
Skill
/goal-clear
Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted.
Install
$ npx -y skills add bonfire-systems/goalkeeper --skill goal-clear --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/goal-clear
Context preview
The summary Claude sees to decide when to auto-load this skill.
Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted.
SKILL.md
goal-clear.SKILL.mdname: goal-clear
description: Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted.
You are operating the **goal-clear** skill. The gk CLI is `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py"`, abbreviated `gk`.
Flow
1. Run `gk status` to see the active goal and its status. No active goal → tell the user and stop. 2. **Confirm via AskUserQuestion** before archiving (unless the goal is already `done` — then clear is just bookkeeping):
- **Archive and clear (Recommended)** — proceed.
- **Cancel** — abort, no changes.
3. Run `gk clear --yes`. gk appends the final log entry, moves the goal directory to `.claude/goals/_archive/<slug>-<timestamp>/`, writes the terminal `active.json`, and — if a chain is in flight — marks it `aborted` without advancing (unreached links' contracts stay in place for re-use). 4. Relay gk's output: the archive path, and that `/goal` or `/goal-prep` starts a new goal.
Hard rules
- **Never delete files.** gk always archives; nothing is removed.
- **Never run `gk clear --yes` without the user's confirmation** (except for an already-`done` goal). The `--yes` flag exists so gk knows the question was asked — it is not a license to skip it.
- **Clearing kills any active chain** — chains are not auto-resumed mid-stream.
Read more
name: goal-clear description: Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted.
You are operating the **goal-clear** skill. The gk CLI is `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py"`, abbreviated `gk`.
Flow
1. Run `gk status` to see the active goal and its status. No active goal → tell the user and stop. 2. **Confirm via AskUserQuestion** before archiving (unless the goal is already `done` — then clear is just bookkeeping):
- **Archive and clear (Recommended)** — proceed.
- **Cancel** — abort, no changes.
3. Run `gk clear --yes`. gk appends the final log entry, moves the goal directory to `.claude/goals/_archive/<slug>-<timestamp>/`, writes the terminal `active.json`, and — if a chain is in flight — marks it `aborted` without advancing (unreached links' contracts stay in place for re-use). 4. Relay gk's output: the archive path, and that `/goal` or `/goal-prep` starts a new goal.
Hard rules
- **Never delete files.** gk always archives; nothing is removed.
- **Never run `gk clear --yes` without the user's confirmation** (except for an already-`done` goal). The `--yes` flag exists so gk knows the question was asked — it is not a license to skip it.
- **Clearing kills any active chain** — chains are not auto-resumed mid-stream.
Ships withgoalkeeper
Durable contract-driven goal execution for Claude Code. A subagent judge gates completion against an explicit Definition of Done.
Get the whole plugin
Stats
13
Stars
2
Forks
Active
Maintenance
Python
Language
MIT
License
16d ago
Last commit
4mo ago
Created
Repo: bonfire-systems/goalkeeper
Other skills on goalkeeper.
@bonfire-systemsView SkillSkill
goal-judge
The gate. Reviews the active goalkeeper goal against its definition-of-done and either approves (advance / mark done) or rejects (with a structured fix-list).…
@bonfire-systemsView SkillSkill
goal-pause
Pause the currently active goalkeeper goal without losing state. Use when the user invokes /goal-pause. The goal can later be resumed with /goal-resume.
@bonfire-systemsView SkillSkill
goal-prep
Interactively draft a goalkeeper contract before executing. Use this skill when the user invokes /goal-prep "<rough idea>", or when /goal is called for a slug…
@bonfire-systemsView SkillSkill
goal-resume
Resume a paused or needs_human goalkeeper goal. Use when the user invokes /goal-resume after they've manually unblocked the goal (e.g. fixed a problem the…
@bonfire-systemsView SkillSkill
goal-supervisor
The mission-level supervisor. One level above goals. Reads the user's mission charter and the most-recently-completed goal's artifacts, then decides whether to…
@bonfire-systemsView Skill