Skip to content
Skills Library
AI & agents · Planning

codex-architect

/codex-architect

Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.

Licence
MIT
Last repository change
08.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.

Original author description

Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.

How it works

  1. Trigger
  2. When NOT to Use
  3. Usage
  4. Modes
  5. Core Principle
  6. Codex Prompt Template
  7. Question
  8. Mode
  9. IMPORTANT: You must independently research the project
  10. Output Requirements
Original SKILL.md headings · 106 lines, 432 words
SKILL.md preview
---
name: codex-architect
description: "Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations."
allowed-tools: Read, Grep, Glob, Agent, Bash(node:*), Write
---

# Codex Architect Skill (Third Brain)

## Trigger

- Keywords: architecture design, solution evaluation, tech selection, third brain, Codex advice, design consulting, ask Codex, second opinion

## When NOT to Use

- Code implementation (use /codex-implement)
- Code review (use /codex-review)
- Deep discussion/exhaustive exploration (use /codex-brainstorm)

## Usage

```bash
/codex-architect "<question>"
/codex-architect "Evaluate this design" --context src/xxx.ts --mode review
/codex-architect "Redis vs MongoDB?" --mode compare
```

## Modes

| Mode    | Purpose                 | When                       |
| ------- | ----------------------- | -------------------------- |
| design  | Provide design advice   | Starting from scratch (default) |
| review  | Evaluate existing design | Validate solution, find issues |
| compare | Compare multiple options | Tech selection             |

## Core Principle

```
User -> Claude -> Codex -> Integrate
          |         |         |
    Initial thinking  Third perspective  Combined advice
```

## Codex Prompt Template

When dispatching per `@skills/codex-code-review/references/codex-transport.md` § Start, the prompt must include the following:

You are a senior architect. Please provide architecture advice for the following question.

## Question

${QUESTION}

## Mode

${MODE} (design/review/compare)

## IMPORTANT: You must independently research the project

Before providing architecture advice, you **must** perform the following research:

### Research Steps

1. Understand the project structure by discovering it: `ls` at the repository root, then list the directories it actually shows — do not assume a `src/` or `test/unit/` layout; many repositories, this one included, have neither
2. Search related modules: `grep -rn "keyword" . -l | head -10` — rooted at the repository, or at a directory the discovery step above actually surfaced; never at an assumed `src/`
3. Read existing implementations: `cat <relevant files> | head -150`
4. Understand existing architecture patterns and conventions

### Verification Focus

- What does the existing architecture look like?
- What are the existing code style and patterns?
- What similar features can be referenced?

## Output Requirements

1. First describe which files you researched
2. Provide advice based on current project state
3. Consider consistency with existing architecture

...(other review dimensions)


## Workflow Integration

```
/codex-architect -> /tech-spec -> /review-spec -> /codex-implement -> /codex-review-fast
    Design           Plan          Review          Implement          Code Review
```

## Verification

- Report includes Codex advice + Claude perspective
- Consensus and divergence points clearly marked
- Final recommendation integrates both perspectives

## References

- `references/project-knowledge.md` - Project architecture knowledge + report template

## Examples

```
Input: /codex-architect "How to design a high-concurrency cache?"
Action: Codex analysis -> Claude supplement -> Integrated output
```

```
Input: /codex-architect "Any issues with this API design?" --mode review
Action: Codex evaluation -> Claude verification -> Output issues + recommendations
```
Files in this package (2)
  • SKILL.md 4 KB
  • references/project-knowledge.md 2 KB

Versions

The database has no other skills named codex-architect.

Database snapshot: 13.11.2026 · package version c72bd30c624c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95codex-implement
    Implement features via Codex exec. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
  • 85claude-collab
    Use when the user asks to invoke, delegate to, or collaborate with Claude (Claude Code) on any task. Also use PROACTIVELY when handing part of the work to Claude, or an independent non-Codex perspective, would add value — implementation, review, second opinions on code, plans,…
  • 90codex
    Ask OpenAI's Codex CLI for help — a second opinion, a code review or a delegated task. Use when the user says "/codex", "ask Codex", "have Codex do it" or "second opinion".
  • 90codex
    Delegate well-scoped coding, analysis, and review tasks to the OpenAI Codex CLI (gpt-5.5) as a cross-model collaborator. Use for implementation chunks you want a second model to write or cross-check, independent second-opinion review of a design or diff, and applying…
  • 100review
    Delegate a read-only code review to a Codex subagent (GPT 6.1 Sol by default) that inspects code and reports findings without editing anything. Use when the user wants Codex — or "GPT-5.5" — to review, look over, audit, or give a second opinion on a diff, branch, pull request,…
  • 95gpt
    Delegate a task to OpenAI Codex through the Quest CLI runner from Claude-led sessions. Use when the user invokes /gpt, asks to use codex, or wants a second opinion from a different model.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.