decision-log-close-out

Resolves and records append-only decision-log entries in docs/90-DECISIONS-AND-IDEAS.md.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill decision-log-close-out-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-log-close-out
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/decision-log-close-out
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill decision-log-close-out-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining an append-only decision log is error-prone: rows get deleted or renumbered, resolutions lack supporting evidence, new findings get buried in existing rows, and gate sign-offs blur into bookkeeping. This Skill enforces disciplined close-out of entries in docs/90-DECISIONS-AND-IDEAS.md so the log stays a trustworthy, auditable record. ## Core Features & Use Cases - In-place I-row resolution: Appends a resolution marker into the row's own cell, naming the file, commit, or session that closed it, without ever removing or renumbering rows. - New finding capture: Gives every genuinely new gap or follow-up its own I-row, assigning the next unused I-N number by scanning the table rather than guessing. - Batch and gate discipline: Completes same-session batches of I-rows as a single unit and writes gate-scope sign-off lines as explicitly labeled, distinct statements. - Use Case: During a feature close-out, a task tags three open I-rows for resolution and uncovers a new risk; the Skill resolves all three with evidence, adds the new finding as the next I-N row, and records a separate gate-schema sign-off line. ## Quick Start Close out the open I-rows in docs/90-DECISIONS-AND-IDEAS.md for this task, resolving each in place with evidence and adding any new findings as new rows.

Frequently Asked Questions about decision-log-close-out

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

FAQPage Schema
How do I resolve an I-row in an append-only decision log?

Append a resolution marker such as a Resolved note directly into the row's own existing cell, naming the file, commit, or session that closed it. Never delete the row, renumber it, or flip the status without supporting detail.

How do I add a new finding to a decision log without duplicating entries?

Scan the parking-lot table for the highest I-N number already assigned, then add the finding as a new row using the next integer in the table's own column format. Folding it into an existing row's notes does not count as recording it.

Can I split a batch of I-row resolutions across multiple sessions?

No. When a task names several I-rows to resolve together, the log-discipline rule treats that batch as a single unit, so every named row must be resolved within the same session before finishing.

What must a gate-scope sign-off line contain?

It must be its own explicit line stating exactly what was checked and found negative for, kept visibly distinct from adjacent bookkeeping or coverage proof even when both share the same table cell or paragraph.

When should this decision-log close-out skill be triggered?

It is injected when a task's tags include decision-log, docs-90, close-out, i-row, sign-off, or fr-015, typically during feature close-out phases in a spec-driven development pipeline.