This repository packages a practical software-engineering toolkit for Codex. It combines governed planning workflows, reusable Codex-authoring workflows, local RAG research helpers, and project-scoped custom agents. Together, these components help a team move from an engineering concept to reviewable design and implementation work while keeping decisions, plans, and evidence in the repository.
The repository is a local Codex marketplace: .agents/plugins/marketplace.json exposes the three plugin packages under plugins/.
- Governed SWE process —
swe-processprovides concept-to-design, ADR, phase-plan, feature-plan, and implementation orchestration workflows using the repository's.swe/layout. - Codex solution authoring —
swe-codexprovides focused workflows for creating or evolving Codex plugins, skills, and native custom agents. - Local RAG research helpers —
local-rag-skillssupplies read-only skills for source discovery, status checks, indexing verification, and evidence retrieval through a Local RAG MCP Server. - Project customizations —
.codex/config.tomlregisters specialist custom agents and project-level Codex settings. - Reviewable engineering artifacts —
.codex/AGENTS.mddefines the canonical.swe/artifact layout and the progression from concept through implementation evidence.
.agents/plugins/marketplace.json Local marketplace listing
.codex/ Codex configuration, custom agents, and workflow governance
.swe/ Durable engineering artifacts created by SWE Process workflows
plugins/
swe-process/ Governed SWE planning and execution skills
swe-codex/ Codex plugin, skill, and agent authoring skills
local-rag-skills/ Read-only Local RAG research skills and MCP configuration
Each plugin has a .codex-plugin/plugin.json manifest and a skills/ directory. The marketplace currently makes these packages available:
| Plugin | Purpose | Included skills |
|---|---|---|
swe-process |
Create governed design, ADR, planning, feature, and execution artifacts. | swe-design, swe-plan, swe-feature, swe-code, orchestrate, orchestrate-max |
swe-codex |
Create and maintain Codex-native plugins, skills, and agents. | new-plugin, new-skill, new-agent |
local-rag-skills |
Research indexed local sources through the configured Local RAG MCP server. | local-rag-search, local-rag-evidence-retrieval, source/status/indexing helpers, and repository reconnaissance |
The repository's .codex configuration is a first-class part of the solution. Its specialist agents support architecture, implementation, infrastructure, agent/skill design, and documentation work. Choose the narrowest agent that fits the task; their definitive scope and instructions live in .codex/agents/core/.
| Agent area | Agents | Primary responsibility |
|---|---|---|
| Architecture and context | solution-architect, context-engineer, jr-context-engineer |
System architecture and context, prompt, workflow, and Codex-instruction design. |
| Codex solution engineering | codex-engineer |
Builds and validates project-scoped Codex plugins, skills, agents, and related configuration. |
| Application and platform work | csharp-developer, full-stack-developer, maf-developer, ui-designer, azure-engineer, azure-db-developer |
Application, UI, Microsoft Agent Framework, Azure infrastructure, and Azure data work. |
| Documentation | code-commenter, repo-author, social-author |
Code-local comments and documentation; repositoryAGENTS.md workflow rules and human-facing README.md files, respectively. |
- A Codex environment that supports local plugin marketplaces and project
.codexconfiguration. - A local checkout of this repository.
- For
local-rag-skills, a running Local RAG MCP server at the endpoint configured inplugins/local-rag-skills/.mcp.json. Its bearer token, when required, is supplied throughLOCALRAG_MCP_TOKENrather than committed to the repository. - For graph navigation, install the
codebase memory mcpcodex plugin.
- In your Codex environment, add this checkout's local marketplace descriptor.
- Install or enable the plugin package needed for the task:
swe-process,swe-codex, orlocal-rag-skills. - Open the repository as a trusted project so Codex can load its project configuration and custom agents.
The repository does not define a package-manager install, build, or test command. Plugin metadata, skill instructions, and project configuration are the distributable artifacts.
- Use
$swe-designwhen concept artifacts in.swe/00-CONCEPT/are ready to become a reviewable design and associated ADRs. - Use
$swe-planto turn an approved design into a phase plan and implementation-ready feature work. - Use
$swe-featureto prepare one independently verifiable feature plan. - Use
$new-plugin,$new-skill, or$new-agentwhen extending a Codex solution. - Use the
local-rag-*skills to discover and gather bounded evidence from an indexed local source before making a code decision.
When changing this repository, read .codex/AGENTS.md first. It governs the required SWE artifact lifecycle, canonical output paths, evidence expectations, and authorization boundaries.
For plugin changes, validate the affected manifest, skill front matter, referenced paths, and marketplace entry. For custom-agent changes, validate the TOML configuration and confirm the corresponding entry in .codex/config.toml. Keep marketplace paths relative to the repository and keep credentials out of tracked files.
Keep changes scoped to the plugin, skill, or agent being improved. Do not modify immutable templates in skill references/ directories to represent project-specific work; copy them to the canonical .swe/ destination instead. Treat resulting designs, ADRs, plans, and feature documents as review candidates until a reviewer explicitly accepts them.