spec-loop
github.com/dpolivaev/spec-loop
Skill | Added | Review |
|---|---|---|
spec-loop-plan-task Choose the route for new work and plan it before implementation. Use this skill to decide whether the work is taskless, chat-only, or task-file, and to create the needed plan for non-trivial executable work. | 48 Impact — No eval scenarios have been run Securityby  Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-prepare-implementation-approval 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 that task for evaluation, feedback, review, or implementation approval. | 34 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-setup-doc-rendering 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. | 56 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-write-glossary Create or update glossary entries in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires a glossary artifact. This skill is mandatory for AsciiDoc glossaries unless the user explicitly opts out for the current project or session. | 52 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-implementation-flow Use this skill after implementation approval for an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint. | 40 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-clarify-task Clarify a proposed task, plan, or design update by interrogating the highest-value unresolved decisions until the inputs are ready for task creation, task planning, or task/design updates. Use this as the default clarification path for Spec Loop task creation, task updates, and any planning, approval, or implementation step that encounters material unresolved questions that are user-preference-sensitive or could materially change scope, constraints, design, or test specification. When clarification ends, resume the invoking workflow. It may also be used for general grilling when explicitly selected or when no other default grilling skill is available. | 62 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 90f996e | |
spec-loop-assess-pull-request Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed. | 48 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: 90f996e |