/hoyeon-blueprint

Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.

BOOST

team-attention@team-attention

GitHub

From plugin

hoyeon

17337 skills29 agents7 hooks

Install

$ npx -y skills add team-attention/hoyeon --skill hoyeon-blueprint --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/hoyeon-blueprint

Context preview

The summary Claude sees to decide when to auto-load this skill.

Hoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.

SKILL.md

hoyeon-blueprint.SKILL.md

name: hoyeon-blueprint
description: |
  Hoyeon blueprint workflow for Codex. Use when the user invokes
  "$hoyeon-blueprint" or wants to turn requirements.md into a validated
  plan.json and optional contracts.md. This adapter loads the canonical
  blueprint skill and follows its Codex runtime surface.

hoyeon-blueprint

This is the Codex-facing wrapper for Hoyeon's canonical `blueprint` skill.

Canonical skill:

Installed root: `__HOYEON_PLUGIN_ROOT__/skills/blueprint/SKILL.md`
Repo-local fallback: `skills/blueprint/SKILL.md` from the current Hoyeon repo

When this skill is invoked:

1. Read the canonical skill file above before executing the workflow. 2. Follow the `Runtime Surface` -> `Codex` section in that file. 3. Mutate `plan.json` only through `hoyeon-cli plan init|merge|validate`. 4. Prefer temporary JSON files over inline complex JSON. 5. Do not rely on hooks or MCP for Codex v1. 6. Use Hoyeon native-agent adapter names when dispatching subagents: `hoyeon-code-explorer`, `hoyeon-worker`, `hoyeon-verifier`, and `hoyeon-code-reviewer`.

The output contract remains the canonical Hoyeon contract: `<spec_dir>/plan.json` and, when useful, `<spec_dir>/contracts.md`.

Read it on GitHub ↗

Ships withhoyeon

All you need is requirements. A Claude Code plugin that derives requirements from your intent, verifies every derivation, and delivers traced code — without you writing a plan. AI can build anything. The hard part is knowing what to build — precisely.

Get the whole plugin

Stats

JavaScript CSS Bash Ruby Git

+6 tags

GitHub Markdown Anthropic OpenAI Gemini MCP

173

Stars

Forks

Maintained

Maintenance

Shell

Language