workflow-en

v0.12.0

Doc-driven multi-agent development workflow (Conductor/Executor/Reviewer three tiers): /scaffold lays down CLAUDE.md + an eight-doc set in place; /whats-next reads the docs and tells you what to do next; sop-generate generates a screenshot-backed business SOP for an already deployed web app; new sessions auto-recognize "wants to build a new project" and silently scaffold it (auto-scaffold, opt-out available); docs-capture — three hook layers auto-log AskUserQuestion decisions to DECISIONS.inbox, nudge on decision/requirement signal words, and gate commits until the inbox is triaged, so key decisions and requirements don't evaporate; the methodology carries a goal ledger (log requirements the same round so they never evaporate), four review disciplines (chained adversarial review / delta-only reports / neutral hardening wording / production red lines in the implementer prompt), internal-first research and component-index registration at wrap-up

Claude Code3 Skills

By Tony Jiang2 GitHub starsUpdated 4 days ago

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Sep 20, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install workflow-en for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install workflow-en@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/7bata/claude-workflow-kit

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/workflow-en/.

Plugin files

plugins/workflow-en/

├── .claude-plugin/plugin.json
├── skills/scaffold/SKILL.md
├── skills/sop-generate/SKILL.md
└── skills/whats-next/SKILL.md

Included Skills3

scaffoldskills/scaffold/SKILL.md

Lay down the methodology scaffolding in place inside the current project directory (CLAUDE.md + the eight-doc set + .gitignore + README). The backend stack is fixed to Go (version baseline in the table inside the skill); Claude decides the database based on project intent. Triggered when the user says "set up scaffolding / initialize project / start new project / scaffold"; also triggered when the user describes wanting to build a new product/tool/website while not currently inside a project directory (Auto mode, paired with the auto-scaffold standing rule).

sop-generateskills/sop-generate/SKILL.md

Generate a screenshot-backed business SOP (operating manual) for any deployed internal web app. Trigger phrases: generate business SOP, operating manual, sop-generate, write an operating procedure doc for this system. Distinguish this from a development-process SOP — this skill produces a manual for "how business staff operate this system," not a code/deployment procedure doc.

whats-nextskills/whats-next/SKILL.md

Determine and report what to do next for a /scaffold project. Triggers when the user says "what's next / what do I do now / whats next / where am I", and the project root has docs/PLAN.md.

Plugin manifests1

plugins/workflow-en/.claude-plugin/plugin.json

{
  "name": "workflow-en",
  "version": "0.12.0",
  "description": "Doc-driven multi-agent development workflow (Conductor/Executor/Reviewer three tiers): /scaffold lays down CLAUDE.md + an eight-doc set in place; /whats-next reads the docs and tells you what to do next; sop-generate generates a screenshot-backed business SOP for an already deployed web app; new sessions auto-recognize \"wants to build a new project\" and silently scaffold it (auto-scaffold, opt-out available); docs-capture — three hook layers auto-log AskUserQuestion decisions to DECISIONS.inbox, nudge on decision/requirement signal words, and gate commits until the inbox is triaged, so key decisions and requirements don't evaporate; the methodology carries a goal ledger (log requirements the same round so they never evaporate), four review disciplines (chained adversarial review / delta-only reports / neutral hardening wording / production red lines in the implementer prompt), internal-first research and component-index registration at wrap-up",
  "author": {
    "name": "Tony Jiang"
  },
  "homepage": "https://github.com/7bata/claude-workflow-kit",
  "keywords": [
    "claude-code",
    "workflow",
    "scaffold",
    "multi-agent",
    "skills"
  ]
}