j.reconcile

Reconciles scrum board statuses against git history, worktrees, and actual code state.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-reconcile-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.reconcile
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-reconcile
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-reconcile-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? AI-assisted development boards drift out of sync with reality: tasks marked Done were never implemented, completed work sits unmarked, orphaned worktree branches go unmerged, and code appears with no board provenance. This Skill audits the Markdown scrum board against git history and the actual codebase, then fixes the drift. ## Core Features & Use Cases - Bidirectional status verification: Demotes completed tasks with no implementation evidence, promotes secretly-implemented tasks to Passed, and merges orphaned worktree branches after confirmation. - Scoped reconciliation: Run a full-board pass or bound the audit to a single epic or a story range (e.g. S03-05) via a deterministic scope resolver script. - Unlinked code detection: Finds tracked files with no board item and no EST-tagged commit behind them, groups them by directory, and offers /uncharted segment for onboarding. - DoD gap reporting and todo cleanup: Flags completed stories with unchecked Definition of Done items and removes or comments out stale entries in project/todo.md. - Use Case: After a big merge session, run the reconcile flow to discover that two 'Done' tasks were never committed, one Pending task is actually implemented, and a new directory has no board item — all corrected in one pass. ## Quick Start Ask the agent to reconcile the board and sync task statuses with what is actually implemented in git.

Frequently Asked Questions about j.reconcile

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

FAQPage Schema
How do I sync a scrum board with actual git implementation state?▼

Run the reconcile flow, which cross-checks every task's board status against git log entries, documentation artefacts, and acceptance criteria. It demotes unimplemented Done items to Pending and promotes verified work to Passed automatically.

How to find code that has no corresponding task or board item?▼

The detect-unlinked-code.sh script scans all tracked files and reports paths with no board reference and no EST-tagged commit that introduced them. Results are grouped by directory so you can onboard them with /uncharted segment.

Can I reconcile only one epic or a range of stories instead of the full board?▼

Yes, pass a scope argument like E12 for a full epic or S03-05 for a story range. Story or task ids resolve to their containing epic, and invalid scopes fail with a clear error before any board file is touched.

What happens to orphaned git worktree branches during reconciliation?▼

When a completed task lacks implementation evidence, the Skill lists matching worktrees and branches and asks for confirmation before merging. Merge conflicts are flagged for manual resolution without changing the task status.

Does reconcile modify board files automatically without review?▼

Status corrections and todo.md cleanup are applied directly, but DoD gaps and unlinked code findings are report-only. Merging branches always requires explicit user confirmation first.