Inakitajes/convoy

Convoy is a higher-level orchestration harness for OpenCode that turns a PRD into a structured, reviewable implementation workflow.

111Stars on the repository
12Mods indexed here, across every type
4d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

Inakitajes/convoy

Skill Claude CodeCodex

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

not rated 111 4d ago A 31 tokens

Inakitajes/convoy

Skill Claude CodeCodex

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

not rated 111 4d ago A 31 tokens

openspec-explore

03

Inakitajes/convoy

Skill Claude CodeCodex

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

not rated 111 4d ago A 39 tokens

openspec-propose

04

Inakitajes/convoy

Skill Claude CodeCodex

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

not rated 111 4d ago A 47 tokens

openspec-sync-specs

05

Inakitajes/convoy

Skill Claude CodeCodex

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

not rated 111 4d ago A 38 tokens

Inakitajes/convoy

Skill Claude CodeCodex

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

not rated 111 4d ago A 55 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: