DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
- 📁 scripts/
- 📄 LICENSE
- 📄 README.md
- 📄 SKILL.md
Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSION_ID.
Implement code incrementally with quality gates. Use when the user says 'build', 'implement', or when starting the implementation phase of an approved plan.
Use this when the user needs to choose between multiple ML routes after survey but before committing to implementation. Compares candidate approaches, selects one, records rejected routes, and keeps a fallback.
Forces the generation of test_assertions.json during the implementation plan phase. v7.2.0 enhanced with severity gates, dependencies, timeouts, and Claw-as-Validator support.
Record implementation pitfalls, debugging insights, and lessons learned into structured devlog documents. Triggers on completing any implementation task that encountered issues, after debugging sessions, after E2E testing, or when user says "record this", "document this pitfall", "add to devlog", "踩坑记录". MUST be invoked after any implementation phase that involved non-trivial bug fixes or workarounds.
- 📄 example-tasks.md
- 📄 existing-task-process.md
- 📄 idea-process.md
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/. --- # Task Analysis Process **Goal: Before writing any code, make sure you understand the requirements and have an implementation plan ready.** ## Ideas and Prototypes _Use this for ideas that are not fully thought out and do not have a fully-formed design/specification and/or implementation-plan._ **For example:** I've got an idea I want to talk through with you before we proceed with the implementation. **Your job:** Help me turn it into a fully formed design, spec, implementation plan, and task list. See [idea-process.md](./idea-process.md). ## Continue WIP Feature _Use this to resume work on a feature that already has design docs and a task list in `/docs/wip/`._ **For example:** Let's continue working on the auth system. **Your job:** Review the current state of the feature, understand what's been done and what's next, then proceed with implementation. See [existing-task-process.md](./existing-task-process.md).
Technical design collaboration through natural dialogue. Adapts to expertise level and problem complexity through understanding, exploration, and validation stages. Use when user asks to brainstorm ideas for new features or systems requiring architectural decisions before implementation begins.
Build apps on Databricks Apps platform. Use when asked to create dashboards, data apps, analytics tools, or visualizations. Invoke BEFORE starting implementation.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- 📁 guardrails/
- 📁 knowledge/
- 📁 pipeline/
- 📄 SKILL.md
Converts an arxiv paper into a minimal, citation-anchored Python implementation. Trigger when user runs /paper2code with an arxiv URL or paper ID, says "implement this paper", or pastes an arxiv link asking for implementation. Flags all ambiguities honestly. Never invents implementation details not stated in the paper.
Fill out the implementation of effects of different attacks, abilities, and trainer cards in this Pokemon TCG Pocket engine codebase.
