skills.rest
viteinfinite
viteinfiniteCOMMUNITY
Explore all skills by this author →
GitHub

openspec-loop

Orchestrate OpenSpec spec implementations with a fresh subagent per spec.

3|Updated Jan 12, 2026
Search Tags:#automation#workflow#isolation#audit#spec#subagent#open-spec
One-click install
npx skills add https://github.com/viteinfinite/skills --skill openspec-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-loop
Source: https://github.com/viteinfinite/skills/tree/main/skills/openspec-loop
Command: npx skills add https://github.com/viteinfinite/skills --skill openspec-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec Loop provides a disciplined, isolated way to implement change proposals by dispatching a fresh subagent for each spec, preventing context bleed and ensuring clean state per task.

Core Features & Use Cases

  • Fresh subagent per spec to avoid cross-contamination
  • Sequential execution with automatic per-spec archiving for auditability
  • Clear, repeatable workflow that scales with multiple specs

Quick Start

Run the OpenSpec Loop to implement all pending specs one by one with a fresh subagent per spec.

Frequently Asked Questions about openspec-loop

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

FAQPage Schema
How do I prevent context bleed when implementing multiple OpenSpec changes sequentially?▼

A fresh subagent per spec prevents context bleed by isolating each OpenSpec change implementation. This sequential execution model maintains clean state per task, ensuring no cross-contamination between independent specs while providing auditable per-spec context tracking.

How does isolated subagent execution work for OpenSpec spec implementations?▼

Isolated subagent execution works by dispatching a new subagent for each pending spec. The orchestrator applies /clear initialization, runs /openspec:apply, and executes /openspec:archive sequentially, ensuring each spec has a clean, focused context window.

Can I use OpenSpec Loop for batch processing multiple independent change proposals?▼

Yes, OpenSpec Loop is designed for batch processing multiple independent OpenSpec changes. It scales with multiple specs by implementing them one by one sequentially, automatically archiving each spec to maintain a clear, repeatable workflow with auditable tracking.

What is the best way to audit context and state for sequential spec implementations?▼

The best way to audit sequential spec implementations is using a fresh subagent per spec with automatic per-spec archiving. This workflow provides auditable per-spec context tracking, ensuring each isolated change is recorded independently after execution.

Do I need to manually clear context between OpenSpec spec executions?▼

No, you do not need to manually clear context. The OpenSpec Loop orchestrator supports automatic /clear initialization between specs, dispatching a fresh subagent per spec to ensure clean, isolated context without manual intervention during sequential execution.

Related Skills

Explore More Software Engineering Skills→
tsediotsedio
43

openspec-continue-change

Create the next OpenSpec workflow artifact based on change status.

Official
Advanced
Strategic-AutomationStrategic-Automation
6

subagent-driven-development

Dispatch independent subagents per task with two-stage reviews before integration.

Official
Advanced
yckkkkyckkkk
1

subagent-driven-development

Dispatch each task to a fresh subagent and enforce two-stage reviews.

Community
Advanced
hetsheth-droidhetsheth-droid

subagent-driven-development

Dispatch fresh subagents per task with isolated context and two-stage reviews.

Community
Advanced