spec-loop

Engage the User to resolve important open decisions in Spec Loop work, including tasks, plans, design updates, work breakdowns, implementation checkpoints, and ADR drafting. Use when the user asks to clarify, compare options, discuss criteria, or stress-test, or when different answers could materially change scope, behavior, policy, constraints, route, Design, Test specification, or ADR content. Provides mandatory decision screening for workflows that require it before dependent Spec Loop content is written or revised. Also use for general grilling when explicitly selected.

Compact an active task file without changing meaning. Use when converting a no-subtask task to subtask form, when adding a new subtask after earlier subtasks already contain full section content, when duplicated section content should be compacted before approval seeking, or when a task file has become too large to use safely.

Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint.

Choose the planning form for new work and plan it before execution. Use this skill to decide whether the work is taskless, chat-only, a task file, a task file with subtasks, or multiple task files / backlog items, and to create the needed plan for non-trivial implementation work or investigation work that needs its own task.

Create or revise file-based Spec Loop work breakdown artifacts for task-file work, including splitting a requested single item into subtasks or multiple task files / backlog items when planning or design shows that split is needed.

Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present task-file work for evaluation, feedback, review, or execution approval.

Review an existing change from a local or user-trusted source, such as a pull request, merge request, branch diff, commit range, or agent-written code. Use when the user needs a merge verdict, a file-wise review walk-through, reconstruction of the change after the fact, or both.

Help set up and troubleshoot rendering for task files and glossary files. Use when the user asks about PlantUML, AsciiDoc, VS Code, Cursor, other VS Code-based IDEs, JetBrains, preview rendering, Java, or Graphviz needed to review rendered task or glossary files.

Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or a Spec Loop workflow routes ADR writing.

Create, update, or supersede a project glossary in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires project glossary work. This skill is mandatory for AsciiDoc project glossaries unless the user explicitly opts out for the current project or session.