objective-refresh

Rebaselines Objective records against verified git evidence without committing changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-lived Objective records drift out of sync with the actual state of a branch or trunk as code, PRs, and plans evolve. This Skill performs a verified rebaseline of active Objective records, correcting stale claims and closing completed Objectives, while never committing anything itself. ## Core Features & Use Cases - Verified rebaseline: Extracts each Objective's contract (purpose, criteria, progress, claims) and forensically verifies every material claim against git history, file probes, and PR evidence before rewriting. - Inline closure with propagation: Closes Objectives whose completion criteria are met, propagating semantic impact to edge-connected counterpart Objectives and running structural checks. - Never-commit guarantee: All edits stay uncommitted in the worktree; the run ends with a compact report of actions per slug (wrote, closed, noop, skipped, closure-ready). - Use Case: Before merging a feature branch, run the refresh so every Objective record under .ns/objectives/ accurately reflects what the branch actually delivers, with stale claims corrected and finished Objectives closed. ## Quick Start Ask the agent to refresh the Objective records for the current feature branch and report which records were rewritten, closed, or skipped.

Frequently Asked Questions about objective-refresh

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

FAQPage Schema
How do I refresh Objective records on a feature branch?

Run the skill with no slug on a feature branch and it selects the union of slugs with committed or uncommitted Objective evidence, using the merge-base with trunk as baseline. It verifies each record's claims and rewrites objective.md and roadmap.md from scratch where the verified contract changed.

Does objective-refresh commit changes to git?

No, the skill never commits or stages anything. All edits remain uncommitted in the worktree, and the final report describes what changed so the user decides how to land it.

When does objective-refresh close an Objective?

It closes an Objective inline when the verified contract shows completion criteria met with no material open work, propagating impact to edge-connected Objectives. It only reports closure-ready without closing when the Objective explicitly requires a final evidence-gathering step.

What happens when a claim in an Objective record cannot be verified?

Unverifiable claims are never kept as fact: they are converted to explicit assumptions or open questions, the roadmap item is parked or narrowed, or the slug is classified skipped-unverified. Semantic Updates never vouch for unverified prose.

Can I refresh a specific Objective by slug?

Yes, pass explicit slugs or paths resolving under .ns/objectives/<slug>/ to refresh exactly those records. On a feature branch, a named slug with no branch evidence is reported not-owned rather than rebaselined against trunk state.