goal-lifecycle

goal-lifecycle is a skill for Claude Code from synaptiai/synapti-marketplace. It costs 138 tokens per session (1,179 once invoked), scanned A, original, Apache-2.0.

A workflow guide for tracking goal status changes together with their audit records in project files.

In plain words
What is it for?
It helps manage goals from draft and active states through waiting, blocked, achieved, failed, or cancelled outcomes.
Why use it?
It prevents lifecycle changes from being made without a matching explanation in the decision history.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Part of the flow plugin — 33 skills, 21 commands, 9 agents shipped together

Good fit It helps manage goals from draft and active states through waiting, blocked, achieved, failed, or cancelled outcomes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/synaptiai/synapti-marketplace/goal-lifecycle
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add synaptiai/synapti-marketplace --skill goal-lifecycle
Clone the repo
git clone --depth 1 https://github.com/synaptiai/synapti-marketplace

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 33 skills, 21 commands, 9 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for goal-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/goal-lifecycle/github.svg)](https://agentmods.dev/skills/synaptiai/synapti-marketplace/goal-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/goal-lifecycle"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/goal-lifecycle/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for goal-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/goal-lifecycle"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/goal-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 138 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,179 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00138 $0.01179
Opus 5 $0.00069 $0.00589
Sonnet 5 $0.00028 $0.00236
Haiku 4.5 $0.00014 $0.00118

Measured 2d ago against content hash 29816d17db4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

goal-lifecycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/flow/skills/goal-lifecycle/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal Lifecycle

Contract

Iron law: no lifecycle.status transition without an audit-trail entry — the goal file changes only through bin/flow-goal-record.sh --update-lifecycle, and every transition writes a goal-created (draft → active) or goal-evaluation journal artifact. Invoked by /flow:goal create, /flow:start Phase 1, and /flow:debug for draft → active after goal-contract-capture; by /flow:goal pause | resume | clear; after /flow:goal evaluate confirms a terminal verdict; and by goal-evaluator for non-terminal updates. Inputs: goal id, from-state, to-state, reason, trigger (evaluator | command | hook | user). Returns the new status once the write and the artifact both succeed. Permitted skip: the run event when scope.run_id is unset. Nothing else.

State machine

Non-terminal: draft, active, and the resumable waiting_for_user, waiting_for_ci, blocked. Terminal and immutable: achieved, failed, cancelled — new work needs a new goal id. The allowed-transition table with triggers, the disallowed transitions, and the last_evaluation.result mapping live in references/goal-lifecycle-transitions.md; bin/flow-goal-record.sh enforces the same table and refuses anything outside it (including terminal → any, active → draft, and blocked → achieved without passing through active).

Outputs

  1. Goal file: lifecycle.status, lifecycle.last_evaluation, optional current_phase / current_activity, turns_evaluated incremented when leaving active for a non-terminal state.
  2. Journal artifact: goal-created for draft → active, goal-evaluation for every other transition.
  3. One lifecycle_transition event in .flow/runs/<run-id>/events.jsonl when run_id is set.

Workflow

  1. Validate — read the goal. If its status differs from the caller's from-state, another process transitioned it: stop and raise the six-field escalation (references/escalation-format.md). Reject a transition outside the table with a stderr explanation and exit 1.
  2. Compose the lifecycle fragment:
    lifecycle:
      status: <to>
      current_phase: <preserved or caller-updated>
      current_activity: <preserved or caller-updated>
      turns_evaluated: <incremented when from=active and to is non-terminal>
      last_evaluation:
        result: <pass | incomplete | fail | needs_human_review | blocked>
        reason: <caller-provided; under 200 chars; comma-safe>
        at: <ISO-8601 UTC now>
    
  3. Writebin/flow-goal-record.sh --update-lifecycle --goal-id <id> --lifecycle-file <fragment> --from-status <from>. The helper takes an O_NOFOLLOW lock, replaces only the lifecycle block, validates against schemas/v1/goal.schema.json when jsonschema is installed, and writes tempfile + rename + fsync. Surface any non-zero exit with its stderr; do not retry blindly — a race means re-reading the state.
  4. Journal — draft → active: bin/journal-record.sh --issue {N} --type goal-created --metadata goal_id=<id> --metadata source=<src>. Otherwise: bin/journal-record.sh --issue {N} --type goal-evaluation --metadata goal_id=<id> --metadata result=<to> --metadata reason=<short>. Ad-hoc goals with no issue write to the session journal .decisions/session-{YYYY-MM-DD}.md.
  5. Run event — when run_id is set, append {"at","type":"lifecycle_transition","goal_id","from","to"} to .flow/runs/<run-id>/events.jsonl; bin/flow-record-activity.sh appends it as part of the FlowActivity the caller records for the phase boundary.

Read the full file on GitHub · 54 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago Changed · -107 lines · -29 tokens per session 29816d17db4c
  2. 9d ago First seen · 161 lines · 167 tokens per session scan A 355153ff4cb5

Subscribe to this mod's changes

goal-lifecycle is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 138 tokens to every session and 1,179 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories