You're using Claude Code. Here's the dynamic workflow.

Claude Code on a paid plan, in a repo you can afford to let agents change. On Pro, turn on Dynamic workflows in /config before step four.

1. 01

   Open a terminal in the project you want reviewed and start Claude Code.

   cd your-project claude

   Use the repo that holds the product you charge for, or want to. The review reads code, config, docs and the deployed pages, so it needs the repo, not a description of it.

2. 02

   Download the commercial readiness skill and unzip it into your skills folder. Claude Code picks it up the next time you type a slash.

   Download the Dynamic Workflows kit~/.claude/skills/commercial-readiness/SKILL.md

   The zip holds the skill folder plus the two prompts as text files. Unzip, then move commercial-readiness into your skills folder. On Windows that folder is C:\Users\you\.claude\skills. Type a slash in Claude Code and look for commercial-readiness in the list to confirm.

3. 03

   Paste the review prompt. Claude Code reads the skill, writes a brief about your product, sends nine agents out at once, and comes back with a verdict and a report.

   Prompt one, the review

   Copy prompt

   Use the commercial-readiness skill to review this repo. Evidence scope is repo plus live: read the code, config and docs, fetch the deployed marketing and legal pages, and check DNS. Never log in to anything and never change anything. Write the report to docs/commercial-readiness.md, copy the brief and the nine lane files into docs/readiness/, and build the report page. Then tell me the verdict, the blocker count, and the three gaps to close first.

   Read the verdict before you go on. Any Blocker means not ready to charge. The three gaps it names first are the ones the workflow hits first.

4. 04

   Paste the workflow prompt, confirm the phases Claude Code shows you, and leave it running.

   /workflows

   Prompt two, the workflow

   Copy prompt

   Use a workflow to close the gaps in docs/commercial-readiness.md. Create a branch named readiness/close-gaps from the current branch and do all of the work there. Phases and gates:
   
   1. Blockers. One agent per gap whose metadata line says Severity: Blocker. Each agent reads only its own gap and closing brief, makes the change, runs that gap's Verify line, and commits with the gap ID first in the subject. Gate: every Blocker's Verify line passes and the project's test command is green.
   
   2. 30-day. The same, one agent per gap whose metadata line says Severity: 30-day. Gate: the same.
   
   3. Review. One agent re-reads every closed gap against its closing brief and reverts any change that does not match the brief. Gate: the reviewer lists each gap as closed or reverted.
   
   4. Re-run. Run the commercial-readiness skill again and write the new report over docs/commercial-readiness.md, so closed gaps move to the Closed table. Gate: zero Blockers remain.
   
   5. Pull request. Open a pull request against the branch I started from, with the Closed table and the reverted list in the description.
   
   Rules for every agent: no deploys, no database migrations, no billing or payment commands, and no new paid service without naming its monthly cost in the pull request. Gaps marked Later stay open. Keep every gap ID unchanged.

   Stay in the same session; a fresh session starts the run over. A run pauses at any permission prompt, so allow the tools your agents need before you start, or run in a mode that does not ask. In the morning, read the pull request, not the transcript.