AI-First Development Methodology v2.0 for Codex CLI — spec-driven pipeline with blocking gates, multi-agent orchestration (spawn_agent/wait_agent), 35 skills, quick-learning knowledge system, and automated validators. Full sync with Claude Code source.
A project-planning process that asks questions, records technical decisions, and fills in the project's documentation. It is designed to complete the project knowledge in one session.
Owner of the unified methodology knowledge system: format, triad structure, similarity check, Seen counters, and Adapted tracking. Signal-gated: skips clean sessions automatically (zero cost). Automatic trigger: called by feature-execution, do-task, and design-generate (context exhaustion). Use when: "quick learning"…
A security review skill based on the OWASP Top 10, a list of common web application security risks. It examines code involving authentication, user input, database queries, and external APIs.
A lightweight way to build a quick software prototype. It asks three to five questions, writes the code directly without checking tools, and then helps decide whether to continue developing or archive it.
Embeds accumulated triads from quick-learning into target skills as permanent instructions. Reads triads with Adapted=— from triad-index.md, analyzes each skill's existing logic, auto-applies new rules when no coverage exists, proposes refinements when partial coverage found. After embedding, updates Adapted field and…
A tool for breaking an approved technical specification into small, separate task files. A technical specification is a document describing what software should do.
A planning tool that creates a tech-spec.md file containing a software design, key decisions, testing approach, and implementation plan. It requires an existing user-spec.md file.
A guide to software testing methods, including which tests to write, how to judge test quality, and how to use the test pyramid. The test pyramid is a model that favours many small tests and fewer large end-to-end tests.
A guided planning process that creates a user-spec.md file, a written description of a feature’s requirements, after scanning the codebase and checking the result twice.
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: