Use this skill when a user wants a bugfix or feature implemented from a specification file, or when a Codex coding task needs a clear spec before execution.

Workflow

Read project instructions first: AGENTS.md and .agent/CONTEXT.md when present.
Check existing specs in sdd/specs/ and proposals in sdd/proposals/ for prior decisions.
Prefer the local SDD template and workflow:
- Template: sdd/templates/spec.md
- Workflow reference: .claude/commands/sdd-spec.md
Create or update a spec with frontmatter that Codex can consume:

---
type: bugfix
repo: ai-parrot
test_command: pytest tests/ -q
files_in_scope:
  - packages/ai-parrot/src/parrot/
  - packages/ai-parrot/tests/
definition_of_done:
  - failing test added
  - bug fixed
  - all tests passing
---

Include a codebase contract with verified file paths, classes, and method signatures.
Keep implementation details precise enough for an autonomous coding provider:
- Problem statement
- Current behavior
- Expected behavior
- Files in scope
- Constraints
- Acceptance criteria
- Validation command
- Known risks
Call code.implement_spec only after the spec is explicit, scoped, and testable.

Guardrails

Do not re-open resolved SDD brainstorm questions.
Do not invent imports, classes, or packages. Verify them in the repository.
Do not ask Codex to make broad unrelated refactors.
Do not omit a validation command when a relevant test target is known.
Treat Codex output as a patch proposal until tests and review confirm it.

Example

await code_toolkit.implement_spec(
    spec_file="specs/bugfix-auth-timeout.md",
    repo_path="/workspace/project",
    test_command="pytest tests/auth -q",
)

Más de este repositorio

mismo repositorio

structured-operation-response

phenobarbital/ai-parrot

How to answer "how do I do X in Odoo?" questions. Use this skill whenever the user asks a how-to or operational question about Odoo (e.g. "how do I create an invoice?", "how do I install a module?"). Responds with an ordered list of concrete, version-aware steps grounded in the PageIndex documentation.

2026-06-1627

install-odoo-module

phenobarbital/ai-parrot

How to install a new Odoo module on the running instance. Use this skill when the user asks to install, enable, or activate an Odoo add-on or module. Covers both shell-based installation via odoo-bin and UI-based installation via the Apps menu.

2026-06-1627

meta-prompting

phenobarbital/ai-parrot

Recursive prompt improvement with quality-driven iteration for Claude Code. Use when you need systematic, measurable improvement of LLM outputs through complexity routing, context extraction, and iterative refinement.

2026-06-1127

agent-browser

phenobarbital/ai-parrot

Automate browser interactions (navigation, form filling, screenshots, data extraction, web-app testing) using a persistent async Playwright session. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from pages. Activate on tasks mentioning "browser automation", "fill a form", "scrape", "screenshot a page", "test the web app", or "click through a site".

2026-06-0527

code-review

phenobarbital/ai-parrot

Reviews code changes and provides feedback, code style and best practices.

2026-04-0327

build-cython-ext

phenobarbital/ai-parrot

Guidance for building and installing Cython extension packages, particularly when resolving compatibility issues with modern Python and NumPy versions. This skill applies when installing legacy Cython packages, fixing NumPy 2.0 deprecation errors, resolving Python 3.x compatibility issues in extension modules, or troubleshooting Cython compilation failures. Use this skill for tasks involving setup.py with Cython extensions, deprecated NumPy type errors, or installing packages to system Python environments.

2026-04-0327

name	codex-specifications
description	Create and refine specification files for Codex-driven implementation through CodeToolkit.

Codex Specifications Skill

Use this skill when a user wants a bugfix or feature implemented from a specification file, or when a Codex coding task needs a clear spec before execution.

Workflow

Read project instructions first: AGENTS.md and .agent/CONTEXT.md when present.
Check existing specs in sdd/specs/ and proposals in sdd/proposals/ for prior decisions.
Prefer the local SDD template and workflow:
- Template: sdd/templates/spec.md
- Workflow reference: .claude/commands/sdd-spec.md
Create or update a spec with frontmatter that Codex can consume:

---
type: bugfix
repo: ai-parrot
test_command: pytest tests/ -q
files_in_scope:
  - packages/ai-parrot/src/parrot/
  - packages/ai-parrot/tests/
definition_of_done:
  - failing test added
  - bug fixed
  - all tests passing
---

Include a codebase contract with verified file paths, classes, and method signatures.
Keep implementation details precise enough for an autonomous coding provider:
- Problem statement
- Current behavior
- Expected behavior
- Files in scope
- Constraints
- Acceptance criteria
- Validation command
- Known risks
Call code.implement_spec only after the spec is explicit, scoped, and testable.

Guardrails

Do not re-open resolved SDD brainstorm questions.
Do not invent imports, classes, or packages. Verify them in the repository.
Do not ask Codex to make broad unrelated refactors.
Do not omit a validation command when a relevant test target is known.
Treat Codex output as a patch proposal until tests and review confirm it.

Example

await code_toolkit.implement_spec(
    spec_file="specs/bugfix-auth-timeout.md",
    repo_path="/workspace/project",
    test_command="pytest tests/auth -q",
)