Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls.

MITAuto-check passed

Install Control Plan

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill control-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins control-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/RBraga01/Quality-Engineering-Skills/skills/planning/control-plan .claude/skills/control-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
control-plan
GitHub stars
1.2k
Token cost
~2.4k tokens
SKILL.md length
1,130 words
Files
2 (incl. references)
Skills in repo
686
Repo updated
First seen
Licence
MIT

At a glance

Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls.

  • Works in 6 steps: Determine the CP type → Build the Control Plan structure → Populate from PFMEA → …
  • Creating a new control plan
  • SKILL.md covers When to use, Prerequisites, Workflow and Validation criteria, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Control Plan is an agent skill from hashgraph-online/awesome-codex-plugins. Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls. Use when creating a new control plan, updating after a process change or corrective action, or auditing an existing CP for completeness and PFMEA alignment. Covers AIAG Control Plan reference manual and IATF 16949 §8.5.1.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/control-plan-template.md`).

The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.

When your agent uses it

  • Creating a new control plan
  • Updating after a process change
  • Corrective action
  • Auditing an existing CP for completeness and PFMEA alignment

Example prompts

  • “/control-plan”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Determine the CP type
  2. Build the Control Plan structure
  3. Populate from PFMEA
  4. Special characteristics — mandatory coverage
  5. Reaction plan requirements
  6. Audit an existing Control Plan

What it can do on your machine

Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Control Plan loads about 2.4k tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 1,130 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its MIT licence (© hashgraph-online). 1,130 words, ~2,356 tokens.

Download SKILL.mdSave it as .claude/skills/control-plan/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
control-plan
description
Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls. Use when creating a new control plan, updating after a process change or corrective action, or auditing an existing CP for completeness and PFMEA alignment. Covers AIAG Control Plan reference manual and IATF 16949 §8.5.1.
license
MIT
metadata.author
RBraga01
metadata.version
1.1
metadata.iso-9001
8.5.1
metadata.iatf-16949
8.5.1
metadata.aiag-reference
AIAG Control Plan Reference Manual
metadata.domain
quality-engineering
metadata.subdomain
planning
metadata.industries
automotive,electronics,aerospace,medical,general
metadata.status
approved

Control Plan

When to use

Use this skill when:

  • Creating a new Control Plan for prototype, pre-launch, or production
  • Reviewing an existing Control Plan for completeness and accuracy
  • Updating the CP after a process change, corrective action (D7), or PFMEA update
  • Auditing a supplier's Control Plan during qualification or an IATF audit
  • Linking PFMEA controls to the Control Plan after FMEA review

Prerequisites

  • Process Flow Diagram (required — CP must mirror the process flow sequence)
  • PFMEA (required — CP controls derive from PFMEA recommended actions)
  • Drawing with ballooned characteristics and tolerance data
  • List of special and significant characteristics (SC, CC, KPC, KCC)
  • MSA results for measurement systems referenced in the CP (for production CP)

Workflow

Step 1 — Determine the CP type
TypeWhenPurpose
PrototypeDuring prototype buildsDescribes dimensional, material, and functional tests in prototype phase
Pre-launchAfter prototype, before PPAPDescribes controls in place during pilot/pre-production runs
ProductionAfter PPAP approval, at SOPThe living document — updated throughout product life

All three types may coexist during APQP phases. The Production CP is the one submitted as PPAP Element 7.

Step 2 — Build the Control Plan structure

The CP is a table with one row per characteristic per process step. Each row contains:

Header section (document-level):

  • Control Plan number and revision
  • Part number and revision
  • Part name / description
  • Supplier / plant
  • Supplier code (OEM code)
  • Key contact / phone
  • Core team (multi-functional)
  • Date (original) and date (revised)
  • Customer engineering approval (name/date) — if required
  • Customer quality approval (name/date) — if required
  • Supplier approval (name/date)

Detail columns (one row per characteristic):

ColumnWhat to enter
Part/process numberReference number from Process Flow
Process name / operation descriptionName of the process step
Machine, device, jig, or toolEquipment used at this step
NumberCharacteristic number (links to balloon drawing)
Product characteristicProduct feature being controlled (dimension, material property, appearance)
Process characteristicProcess parameter being controlled (temperature, pressure, speed, torque)
Special characteristic classificationSC, CC, KPC, KCC, *, ▲ per customer symbology
Product/process specification / toleranceNominal value and tolerance band
Evaluation / measurement techniqueGauge type, method, or test used
Sample sizeNumber of parts per sample
FrequencyHow often samples are taken (every hour, every lot, 100%)
Control methodHow the process is controlled (SPC chart, go/no-go gauge, visual, 100% inspection)
Reaction planWhat to do if out-of-control or out-of-specification (who, what action, containment)
Step 3 — Populate from PFMEA

For each high-severity failure mode in the PFMEA:

  1. Identify the current prevention and detection controls from the PFMEA
  2. Transfer these controls into the corresponding CP row
  3. The reaction plan must address what happens if the control detects a non-conformance

Every special characteristic (SC, CC, ★, ◆) in the PFMEA must appear in the CP. Every recommended action completed in the PFMEA must be reflected in the updated CP controls.

Step 4 — Special characteristics — mandatory coverage
ClassificationOEM symbolCP requirement
Safety / Regulatory★ SC / ⬟100% inspection OR demonstrated Cpk ≥ 1.67 + statistical monitoring
Critical CharacteristicCC / ◆Same as above — automatic stop if out of spec
Significant CharacteristicSC (Ford) / KPCProcess monitoring with defined sample plan and reaction
Key Control CharacteristicKCCProcess parameter monitoring (not product) — SPC or other control

OEM symbol conventions vary. Always use the exact symbol specified in the customer's CSR:

  • Ford: CC (Critical Characteristic) and SC (Significant Characteristic) — do not use ★ or ◆
  • GM: ★ for safety-critical; Δ for significant
  • VW / Audi: D (design feature, = CC), E (significant characteristic), I (functional dimension) per FORMEL Q
  • BMW: G-SC (significant characteristic), G-CC (critical characteristic) per BMW standard
  • Stellantis: CC and SC per MAQMSR — requires AIAG-VDA FMEA format alignment

Using the wrong symbol for the customer's OEM is an immediate finding at PPAP and IATF audit.

For all special characteristics: the reaction plan must specify who is notified, containment action, and when the process can restart.

Step 5 — Reaction plan requirements

Every row in the CP must have a reaction plan. Minimum requirements:

  • Who is responsible for taking action
  • What immediate containment is applied (tag, sort, hold, stop production)
  • Who is notified (supervisor, quality, engineering)
  • When production may restart (after what verification)
  • Reference to relevant Work Instruction or SOP for the reaction

A reaction plan that says only "notify supervisor" or "quarantine parts" is insufficient — it must specify the next step after notification.

Show full SKILL.md (429 more words)Show less
Step 6 — Audit an existing Control Plan

When reviewing a supplier's or internal CP, check:

Structure:

  • All process steps from the Process Flow are represented
  • Each special characteristic has its own dedicated row
  • Revision level matches the current PFMEA and drawing revision

Characteristics:

  • All SC/CC/KPC/KCC are listed with correct classification symbols
  • Product AND process characteristics are both covered (not just product)
  • Tolerances match the current released drawing

Controls:

  • Measurement technique is specific (gauge type, not just "measure")
  • Sample size and frequency are defined (not "as required" or "as needed")
  • 100% inspection is specified where Cpk < 1.33
  • SPC control charts are specified for characteristics where they are required

Reaction plan:

  • Every row has a reaction plan
  • Reaction plans specify concrete actions (not just "notify supervisor")
  • Reaction plans are consistent with PFMEA failure mode severity

Alignment:

  • CP controls match PFMEA current controls column for each failure mode
  • Completed PFMEA recommended actions are reflected in updated controls
  • CP revision date is more recent than most recent PFMEA update date

Validation criteria

A complete Production Control Plan for PPAP submission must:

  • Cover every operation in the Process Flow
  • Include every special and significant characteristic with correct classification
  • Have a MSA-validated measurement system for every variable characteristic on SC/CC
  • Have a reaction plan for every row
  • Be signed by the APQP team (multi-functional) and have customer approval if required
  • Match the PFMEA revision level

Common mistakes

  • Control Plan created without reference to PFMEA — controls are generic, not linked to actual failure modes
  • Reaction plan says "notify supervisor" only — not a reaction plan, just escalation
  • Missing process characteristics — CP only controls product dimensions, not process parameters like temperature or torque
  • Sample plan says "as required" — must specify a number and frequency
  • SC/CC characteristics not identified with correct customer symbol — auditor will flag this immediately
  • CP not updated after D7 of an 8D — the most common disconnect in corrective action systems
  • Gauge type not specified — "visual inspection" or "measure" is not sufficient; must name the tool

Output Format

At the start of each use, ask the user:

"How would you like to receive the output? A — Structured Markdown (formatted tables and sections, ready to copy) B — Plain tables (simplified structure for Excel or Word) C — Narrative report (flowing text for a formal document or email)

Default: A."

Adapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.

Changelog

VersionDateAuthorChange
1.02026-06-06@RBraga01Initial release
1.12026-06-06@migmccAdded OEM-specific special characteristic symbol conventions (Ford, GM, VW, BMW, Stellantis) in Step 4

© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/RBraga01/Quality-Engineering-Skills/skills/planning/control-plan of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/control-plan-template.md

Open the folder on GitHubat commit 78497e5

Compare with similar skills

Control Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Control Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Control Plan this skillhashgraph-online/awesome-codex-plugins1.2k—~2.4kAutomated safety check: PassMIT
PrototypeDonchitos/Claude-Code-Game-Studios26k—~8.1kAutomated safety check: NotesMIT
PrototypeEpicenterHQ/epicenter4.8k—~767Automated safety check: PassCustom licence
Prototypevinvcn/mattpocock-skills-zh-CN4.7k—~406Automated safety check: PassMIT
Prototypefossasia/eventyay-interpretation1.6k36 repos~755Automated safety check: PassApache-2.0
Prototypeplugin87/ux-ui-agent-skills1.5k—~614Automated safety check: PassMIT

Similar skills

  • Prototype

    Donchitos/Claude-Code-Game-Studios

    Concept prototype before GDDs — throwaway HTML, Engine or Paper build, PROCEED/PIVOT/KILL/NOT ASSESSED.

    26k GitHub stars~8.1k tokensUpdated 9 days ago
    Game DevelopmentAuto-check: notes
  • Prototype

    EpicenterHQ/epicenter

    Build a throwaway prototype to answer a focused logic, state-model, or UI question before committing to production design.

    4.8k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed
  • Prototype

    vinvcn/mattpocock-skills-zh-CN

    构建一次性原型来回答一个设计问题。适用于用户想验证某个 state model 或 logic 是否感觉对,或探索 UI 应该长什么样时。

    4.7k GitHub stars~406 tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • Prototype

    fossasia/eventyay-interpretation

    Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

    1.6k GitHub starsUsed in 36 repos~755 tokens
    DevelopmentAuto-check passed
  • Prototype

    plugin87/ux-ui-agent-skills

    Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.

    1.5k GitHub stars~614 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Prototype

    nodetool-ai/nodetool

    Build a runnable prototype to answer a logic, state, or UI design question.

    556 GitHub stars~723 tokensUpdated today
    Frontend & DesignAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed
  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Questions about Control Plan

What does Control Plan do?

Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls. Control Plan is an agent skill from hashgraph-online/awesome-codex-plugins. Control Plan — build, review, or audit a Prototype, Pre-launch, or Production Control Plan linked to PFMEA failure modes and controls.

When should I use Control Plan?

Control Plan fits situations like: creating a new control plan; updating after a process change; corrective action; auditing an existing CP for completeness and PFMEA alignment.

How do I install Control Plan in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill control-plan -a claude-code`. Or copy the skill folder (plugins/RBraga01/Quality-Engineering-Skills/skills/planning/control-plan in hashgraph-online/awesome-codex-plugins) into .claude/skills/control-plan in your project. Claude Code loads it when a task matches its description.

How do I install Control Plan in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill control-plan -a codex`. Or copy the skill folder (plugins/RBraga01/Quality-Engineering-Skills/skills/planning/control-plan in hashgraph-online/awesome-codex-plugins) into .agents/skills/control-plan in your project. Codex loads it when a task matches its description.

Can I use Control Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill control-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/control-plan, .gemini/skills/control-plan, .github/skills/control-plan and .opencode/skills/control-plan in your project.

What does Control Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Control Plan is instructions for the agent only.

Does Control Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Control Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Control Plan use?

Control Plan is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Control Plan use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.3k tokens, read only when the agent opens those files.

What are the alternatives to Control Plan?

Skills that share tags, products or a category with Control Plan: Prototype (Donchitos/Claude-Code-Game-Studios, 26k stars), Prototype (EpicenterHQ/epicenter, 4.8k stars), Prototype (vinvcn/mattpocock-skills-zh-CN, 4.7k stars) and Prototype (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Control Plan?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.