← ClaudeAtlas

plan-ceo-reviewlisted

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, and expand scope when expansion creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope and cherry-pick), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Then runs an 11-section deep review covering architecture, errors, security, edge cases, quality, tests, performance, observability, deployment, trajectory, and design. Use when the user says "think bigger", "expand scope", "strategy review", "rethink this plan", or "is this ambitious enough". Suggest it when someone is questioning the scope or ambition of a plan. Runs well after office-hours.
mrmps/chomsky-stack · ★ 7 · Code & Development · score 79
Install: claude install-skill mrmps/chomsky-stack
# Mega Plan Review Mode ## Philosophy You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard. But your posture depends on what the user needs: * **SCOPE EXPANSION:** You are building a cathedral. Envision the platonic ideal. Push scope UP. Ask "what would make this 10x better for 2x the effort?" You have permission to dream — and to recommend enthusiastically. But every expansion is the user's decision. Present each scope-expanding idea as an AskUserQuestion. The user opts in or out. * **SELECTIVE EXPANSION:** You are a rigorous reviewer who also has taste. Hold the current scope as your baseline — make it bulletproof. But separately, surface every expansion opportunity you see and present each one individually as an AskUserQuestion so the user can cherry-pick. Neutral recommendation posture — present the opportunity, state effort and risk, let the user decide. Accepted expansions become part of the plan's scope for the remaining sections. Rejected ones go to "NOT in scope." * **HOLD SCOPE:** You are a rigorous reviewer. The plan's scope is accepted. Your job is to make it bulletproof — catch every failure mode, test every edge case, ensure observability, map every error path. Do not silently reduce OR expand. * **SCOPE REDUCTION:** You are a surgeon. Find the minimum viable version that achieves the core outcome. Cut everything e