القائمة
Use when systematically implementing OpenSpec change proposals through clean, sequential delegation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when systematically implementing LightSpec change proposals through clean, sequential delegation
Recorder CLI skill that captures HTTP payloads during debugging sessions and allows to review and log recent requests quickly.
Start and stop a server with pm2 using `pm2 start ./my-server --name <name> --no-autorestart`, plus common supporting commands for status, logs, restart, and cleanup.
Use when creating git commits. Learns repository-specific commit style patterns from history, caches them, and enforces consistency.
Use when implementing features, refactors, or fixes that affect core functionality, configuration, infrastructure, or integrations. Ensures documentation stays accurate by updating README, operational guides, and reference docs, and verifying links/commands remain correct.
| name | openspec-loop |
| description | Use when systematically implementing OpenSpec change proposals through clean, sequential delegation |
Implement OpenSpec specs by dispatching fresh subagent per spec, with clean context isolation and sequential execution.
Core principle: Fresh subagent per spec + sequential execution + clean context = high quality isolated implementation
digraph when_to_use {
"Have OpenSpec specs to implement?" [shape=diamond];
"Specs are independent changes?" [shape=diamond];
"Want clean context per spec?" [shape=diamond];
"openspec-subagent-driven-development" [shape=box];
"Manual execution or other workflow" [shape=box];
"Have OpenSpec specs to implement?" -> "Specs are independent changes?" [label="yes"];
"Have OpenSpec specs to implement?" -> "Manual execution or other workflow" [label="no"];
"Specs are independent changes?" -> "Want clean context per spec?" [label="yes"];
"Specs are independent changes?" -> "Manual execution or other workflow" [label="no - tightly coupled"];
"Want clean context per spec?" -> "openspec-subagent-driven-development" [label="yes"];
"Want clean context per spec?" -> "Manual execution or other workflow" [label="no"];
}
Key characteristics:
/cleardigraph process {
rankdir=TB;
"Run 'openspec view' to discover active specs" [shape=box];
"Present active specs to user" [shape=box];
"User confirms implementation order" [shape=box];
"More specs remain?" [shape=diamond];
subgraph cluster_per_spec {
label="Per Spec";
"Dispatch fresh general-purpose subagent" [shape=box];
"Subagent executes /clear" [shape=box];
"Subagent exports context usage" [shape=box];
"Subagent executes /openspec:apply [spec-id]" [shape=box];
"Subagent implements all spec changes using /openspec:apply [spec-id]" [shape=box];
"Subagent archives the spec using /openspec:archive [spec-id]" [shape=box];
"Verify spec archived successfully" [shape=box];
"Report status to user" [shape=box];
}
"Provide implementation summary to user" [shape=box style=filled fillcolor=lightgreen];
"Run 'openspec view' to discover active specs" -> "Present active specs to user";
"Present active specs to user" -> "User confirms implementation order";
"User confirms implementation order" -> "More specs remain?";
"More specs remain?" -> "Dispatch fresh general-purpose subagent" [label="yes"];
"Dispatch fresh general-purpose subagent" -> "Subagent executes /clear";
"Subagent executes /clear" -> "Subagent exports context usage";
"Subagent exports context usage" -> "Subagent executes /openspec:apply [spec-id]";
"Subagent executes /openspec:apply [spec-id]" -> "Subagent implements all spec changes";
"Subagent implements all spec changes" -> "Subagent archives the spec";
"Subagent archives the spec" -> "Verify spec archived successfully";
"Verify spec archived successfully" -> "Report status to user";
"Report status to user" -> "More specs remain?";
"More specs remain?" -> "Provide implementation summary to user" [label="no"];
}
When launching a subagent, provide it with these exact instructions:
You are implementing a specific OpenSpec change proposal. Your workflow:
1. FIRST ACTION: Execute `/clear` to ensure clean context
2. THIRD ACTION: Execute `/openspec:apply [spec-id]` to apply the spec you're implementing
3. Implement all changes described in the spec
4. After successful implementation, archive the spec
5. Report completion and terminate
Spec to implement: [spec-details]
You: I'm using OpenSpec Subagent-Driven Development to implement pending specs.
[Run 'openspec view' and parse active changes]
[Present list to user]
You: Found 3 active specs:
1. add-base-image-uploads
2. add-strapi-tag-creation
3. some-other-feature
User: Implement in this order: add-base-image-uploads, then add-strapi-tag-creation
You: Confirmed. Starting implementation...
=== Spec 1: add-base-image-uploads ===
[Dispatch general-purpose subagent with spec details]
[Subagent executes /clear]
[Subagent exports context usage]
[Subagent executes /openspec:apply add-base-image-uploads]
[Subagent implements changes]
[Subagent archives spec]
[Verify archiving]
You: ✅ add-base-image-uploads completed and archived
=== Spec 2: add-strapi-tag-creation ===
[Dispatch fresh general-purpose subagent with spec details]
[Subagent executes /clear - completely fresh context]
[Subagent exports context usage]
[Subagent executes /openspec:apply add-strapi-tag-creation]
[Subagent implements changes]
[Subagent archives spec]
[Verify archiving]
You: ✅ add-strapi-tag-creation completed and archived
=== Summary ===
All requested specs implemented successfully:
✅ add-base-image-uploads
✅ add-strapi-tag-creation
Remaining: some-other-feature
vs. Manual spec implementation:
vs. Parallel implementation:
Quality benefits:
/clear ensures no mental contaminationNEVER:
/clear action - it's critical for isolationALWAYS:
If subagent fails to implement its spec:
If spec cannot be applied:
Maintain a clear status display showing:
Update after each spec completion.
Required workflow skills:
Related workflows:
Terminate after: