objective-update

Updates tracking records for one Objective after branch or PR changes.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill objective-update-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: objective-update
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/objectives/objective-update
Command: npx skills add https://github.com/nseng-ai/ns --skill objective-update-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping long-running project Objectives accurate is tedious: after landing code or opening a PR, someone must manually record progress, revise assumptions and risks, update roadmap checkboxes, and decide whether the work is done. This Skill automates that bookkeeping for exactly one Objective, using git and PR evidence to write durable, post-landing tracking updates. ## Core Features & Use Cases - Evidence-driven updates: Collects working-tree, branch diff, Graphite parent, and optional GitHub PR evidence, then edits objective.md, roadmap.md, and frontmatter only where meaning actually changed. - Immutable Semantic Updates: Appends timestamped update files under updates/ for material findings while treating existing updates as immutable history. - Closure Gate: Automatically closes an Objective inline when completion criteria are clearly met, propagating impact to connected Objectives. - Use Case: After finishing a feature branch, ask the agent to update the Objective; it inspects the diff, marks completed roadmap rows, records a Semantic Update, re-judges blocked status, and closes the Objective if warranted. ## Quick Start Ask the agent to run objective-update for the current branch so it records progress on the active Objective.

Frequently Asked Questions about objective-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an Objective after finishing a branch?

Invoke objective-update and select one active Objective. The skill collects git status, branch diff against the base, and optional PR evidence, then edits objective.md and roadmap.md and appends a Semantic Update only when meaning changed.

When does objective-update close an Objective automatically?

It auto-closes only when the Closure Gate is clearly met: outcome is evident, completion criteria are evidenced, no active roadmap work remains, and risks are resolved or carried as follow-ups. Ambiguous cases stay open and are reported as skipped-unclear.

Can objective-update modify multiple Objectives at once?

No, it strictly updates one selected Objective per invocation. The only exceptions are mirrored edge frontmatter edits on connected counterparts and close-time propagation when the selected Objective closes inline.

Does objective-update require a GitHub PR to record progress?

No, PR evidence is optional. Local committed branch diffs against the base branch are sufficient; gh CLI output is used only as corroborating evidence when available.

What happens if I try to edit an existing Semantic Update?

Existing Semantic Updates are immutable and are never amended. The skill writes a new corrective update that states the newer meaning and optionally notes that older updates are historical records.