second-claude-code

Use when a vague idea needs Socratic requirements discovery, topology confirmation, ambiguity scoring, and an approval-gated spec before execution

Use when a prompt asset keeps causing the same PDCA gate failure and you want to evolve it against a maintainer-authored structural check

Use when running a PDCA cycle across research, production, review, and refinement

Use when iteratively improving a draft until it meets a review target

Use when reviewing content, strategy, or code with parallel specialized reviewers

Use when a fetched URL returns 4xx/blocked, hits a WAF or captcha, or when a JS-heavy SPA returns no usable body. Escalates through public APIs, Jina Reader, header-diverse curl, TLS impersonation, headless browsers, and free archive mirrors until validated content is returned. Zero API keys.

Use when applying strategic frameworks such as SWOT, RICE, OKR, or GTM

Use when decomposing large tasks into independent parallel units

Use when collecting URLs, notes, files, or excerpts into structured PARA knowledge

Use when the current skills cannot handle a task and new skills are needed

Use when debugging errors, unexpected behavior, or root-cause analysis

Use when benchmarking and evolving prompt assets through a fixed-suite optimization loop

Use when researching a topic through iterative web exploration and synthesis

Use when observing user patterns and synthesizing a persistent identity profile

Use when translating content between English and Korean with formatting preservation

Use when the user asks to open the SCC Artifact Viewer, show artifacts, inspect PDCA pipeline outputs, or after a PDCA pipeline run completes.

Use when chaining multiple /scc commands into a reusable workflow

Use when producing newsletters, articles, reports, shorts, or social content