agentleFS
Sign inStart free
FuDesign2008FuDesign2008/open-skills/skills/design-approval-gate/SKILL.md

design-approval-gate

Skill6 starsChanged 6 days agoMITView on GitHub

Hard gate before production implementation: do not write behavior/production code until the chosen solution/design is approved; named escapes for auto mode, Jira auto/force, and lean hotfix require short 留痕. Referenced by PDCA hosts before execution stages. Triggers — 「设计批准门禁」「方案批准后才能写码」「实现前批准」「design approval gate」 / design approval gate, pre-impl approval. Do NOT use as a name alias for brainstorming.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Manual mode: wait for explicit user pass (or equivalent structured confirmation) on the chosen solution/design before stage-6-style code …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Approval Gate

Internal shared skill. Single source of truth for pre-implementation approval. Hosts declare it in dependencies and abort if missing — no silent fallback.

Name note: intentionally not named brainstorming (external skills repo). Use this name only.

Iron Law

NO PRODUCTION / BEHAVIOR IMPLEMENTATION WITHOUT DESIGN OR SOLUTION APPROVAL.

  • Manual mode: wait for explicit user pass (or equivalent structured confirmation) on the chosen solution/design before stage-6-style code edits.
  • Allowed before approval: OpenSpec / host analysis artifacts; analysis-core analysis-assist temporary edits (must still roll back per that skill).
  • Forbidden before approval: shipping the fix in business/production code; calling implementation skills for the purpose of landing the change.

Named escapes (require 留痕)

These MAY proceed without a human pass; each MUST record a one-line 留痕 (escape name + reason):

EscapeWhen
auto modeHost entered via explicit auto trigger («自动…» / --auto)
Jira auto/forcejira-fix / opsx-jira-fix auto or force path
lean hotfixHost selected lean path with high-certainty hot fix

Not an escape: "this is too simple" / unspoken skip in manual mode.

留痕 template

【设计批准门禁逃生】escape=<auto|jira-auto-force|lean-hotfix>；reason=<short>；time=<ISO>。

Forbidden

  • Silent skip in manual mode without approval or named escape
  • Renaming this skill to brainstorming inside this repository
  • Treating OpenSpec artifact writes as a violation of this gate

Integration guide

  • Hosts: one-line pointer before the execution stage — load this skill; do not paste the escape table into hosts.
  • Prefer user-invocable: false.
  • Compose with workflow-mode-lifecycle: auto escape only when auto mode is actually active.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free