Coordinate Codex-native threads into parallel lanes with ownership and gates.
npx skills add https://github.com/majiayu000/spellbook --skill threads-majiayu000
Please help me install this Agent Skill. Skill: threads Source: https://github.com/majiayu000/spellbook/tree/main/skills/threads Command: npx skills add https://github.com/majiayu000/spellbook --skill threads-majiayu000
Orchestrate Codex-native threads to split broad tasks into parallel lanes with explicit ownership, gates, and verifiable closure, reducing coordination overhead and miscommunication.
Describe the current queue and initiate Codex-native thread planning for a bounded tranche.
High-intent search queries and answers about installing and using this skill.
You can split broad GitHub issue and PR queues into concurrent lanes using Codex-native subagents, each with explicit ownership, base gates, and verifiable closure to reduce coordination overhead and miscommunication.
Lane-based planning divides broad tasks into parallel execution threads with explicit ownership and capability gates. This mechanism maintains auditability through remote truth checks and closure audit workflows for complete end-to-end task resolution.
Enforce a no-merge default by applying truth level management (A-D) and capability gates to each parallel lane. Threads must provide evidence-backed results using prescribed prompts, run logs, and lane outputs before verifiable closure is authorized.
Yes, you can apply Codex-native threads to cross-repo workflows where independent lanes run concurrently. Each thread receives writable files, base gates, and remote truth checks to satisfy constraints like default no-merge and truth level management.
Describe the current queue and initiate Codex-native thread planning for a bounded tranche. This dispatches threads with capability gates and remote truth checks to maintain auditability throughout the closure audit workflow.
Threads require evidence-backed results using prescribed prompts, run logs, and lane outputs for verifiable closure. The default no-merge constraint and truth level management (A-D) must be satisfied, meaning lanes cannot merge without explicit authorization.
rjskeneOrchestrate GitHub-issue-driven CI workflows with classification, planning, execution, and conditional merging.
u9401066Automate single-task workflows through PLAN, EXECUTE, VERIFY, and COMPLETE phases.
hanibalskExecute implementation plans by dispatching fresh subagents with code reviews between tasks.
MohamedAbdallah-14Enforce completion claims with fresh command evidence or deterministic proof paths.
