Skip to content
cccskills
FreePublished on GitHub

pi-goal

Persistent Codex-style goal tracking for pi. Use when the user explicitly asks to set, continue, audit, pause, resume, complete, or inspect a long-running goal.

The English summary is being prepared. Showing the original description.

See how to install

Files included (37)

  • SKILL.md1.1 KB
  • .github/workflows/ci.yml1.4 KB
  • .gitignore60 B
  • biome.json725 B
  • bun.lock63.9 KB
  • CHANGELOG.md1.6 KB
  • LICENSE1.0 KB
  • package-lock.json166.5 KB
  • package.json1.4 KB
  • README.md3.6 KB
  • scripts/check-no-excuse-rules.ts6.0 KB
  • src/goal/command-registration.ts3.7 KB
  • src/goal/command.ts681 B
  • src/goal/continuation.ts432 B
  • src/goal/errors.ts599 B
  • src/goal/format.ts2.6 KB
  • src/goal/lifecycle.ts7.4 KB
  • src/goal/prompt.ts2.4 KB
  • src/goal/store.ts8.7 KB
  • src/goal/tool-registration.ts5.3 KB
  • src/goal/transitions.ts2.0 KB
  • src/goal/turn-usage.ts1.8 KB
  • src/goal/types.ts1.5 KB
  • src/goal/ui.ts771 B
  • src/goal/validation.ts1.9 KB
  • src/index.ts1.3 KB
  • test/command.test.ts1.3 KB
  • test/continuation.test.ts1.9 KB
  • test/extension.test.ts33.8 KB
  • test/format.test.ts2.8 KB
  • test/prompt.test.ts3.5 KB
  • test/store.test.ts12.3 KB
  • test/turn-usage.test.ts1.2 KB
  • test/ui.test.ts1.9 KB
  • test/validation.test.ts1.8 KB
  • tsconfig.json914 B
  • vitest.config.ts132 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

pi-goal

Use goal tools only when the user explicitly wants persistent goal tracking or when an active goal already exists.

Tools

Create a goal:

create_goal({
	objective: "Ship the pi-goal extension",
	token_budget: 50000,
});

Inspect a goal:

get_goal({});

Update a goal:

update_goal({
	status: "complete",
});

update_goal only accepts complete. User-facing /goal commands control pause, resume, budget-limited, and clear transitions.

Completion Rule

Before marking a goal complete, audit the actual current state:

  1. Restate the goal as concrete deliverables.
  2. Map every explicit requirement to real evidence.
  3. Inspect files, command output, test results, or repository state for each item.
  4. Treat uncertainty as incomplete.
  5. Call update_goal({ status: "complete" }) only when no required work remains.

Use budget-limited status when the reason to stop is budget exhaustion rather than completion.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Report a problem with this skill