boilerplate-workflow

Minimal Codex adapter for this repository.

9 stars

Best use case

boilerplate-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Minimal Codex adapter for this repository.

Teams using boilerplate-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/boilerplate-workflow/SKILL.md --create-dirs "https://raw.githubusercontent.com/mlucascosta/ia_boilerplate/main/.agents/runtimes/codex/skills/boilerplate-workflow/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/boilerplate-workflow/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How boilerplate-workflow Compares

Feature / Agent	boilerplate-workflow	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Minimal Codex adapter for this repository.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

Cursor vs Codex for AI Workflows

Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.

SKILL.md Source

# Codex adapter

Follow `.agents/AGENTS.md`.

## Source of truth

1. `.agents/AGENTS.md`
2. `docs/ai/WORKFLOW_SHORT.md`
3. `docs/ai/WORKFLOW.md` only if ambiguous
4. `docs/ai/ARTIFACTS.md`

## First read

- `docs/ai/WORKFLOW_SHORT.md`
- one active artifact: `.planning/STATE.md` or the active plan
- area files selected through `docs/ai/CONTEXT_MAP.md`
- files explicitly requested by the user

If an active plan exists, use it as the local execution guide and keep `STATE.md` as the global header only.

## Max read budget

Before acting, read only the first-read set and the smallest additional area context needed for correctness.
Do not scan the whole repository.
Do not load unrelated docs.

## Path selection

- Trivial: one local change, default `VERIFY=V0`
- Focused: bounded multi-file change, default `VERIFY=V1`
- Full: structural or cross-cutting change, default `VERIFY=V2`

Escalate path if correctness is at risk.

## Git strategy

- Git Flow is mandatory
- Detect the stable branch as `main` or `master`
- `develop` is the default integration and base branch for feature work
- Create `feature/*` branches from `develop`
- Merge feature branches back into `develop`
- Reserve the stable branch for release state
- Use `release/*` for stabilization and `hotfix/*` for urgent production fixes
- Do not work directly on the stable branch for normal feature delivery
- If the stable branch exists but `develop` does not, create `develop` from the stable branch before feature work starts
- If neither `develop` nor a stable branch exists, ask the user to identify the long-lived branches before proceeding, then initialize Git Flow with `develop` as the integration branch

## Output contract

- Return only the minimal diff or patch.
- Add a targeted note only when required for correctness.
- Add the exact next step only when the task remains open.
- Prefer flags and manifests over prose. Do not restate plan flags in natural language.
- No workflow recap.
- No file dumps.
- No context replay.

## Verification contract

- Use `V0` for trivial work, `V1` for focused work, and `V2` for full work.
- Escalate verification when risk exceeds the default path.
- Keep verification explicit and minimal.

## Artifact update rules

- Keep `.planning/` current for phased or risky work.
- Use `docs/ai/DECISION_RULES.md` before touching roadmap, ADRs, or governance docs.
- Preserve documented architecture and avoid undeclared platform shifts.
- Treat chat history as temporary memory only.

## Hard prohibitions

- Inventing a Codex-only workflow.
- Full file pastes.
- Context replay.
- Hidden structural drift.