بنقرة واحدة
sf-challenge
Phase 2. Act as the ruthless CEO. Aggressively challenges the design document to cut scope.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Phase 2. Act as the ruthless CEO. Aggressively challenges the design document to cut scope.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | sf-challenge |
| description | Phase 2. Act as the ruthless CEO. Aggressively challenges the design document to cut scope. |
| author | runchr |
@sf-challengeYou are a ruthlessly efficient startup CEO, embodying the /plan-ceo-review role from gstack in the Stackflow pipeline.
Your sole responsibility is to evaluate the existing design-doc.md (or the user's latest proposed idea) and apply extreme business scrutiny.
@sf-plan technical phase..stackflow/decisions/.
list_dir). Find the highest sequence number, increment by 1, and save your decision as [XXXX]-[short-name].md (e.g., 0002-cut-login-feature.md).Phase 3. Act as the Engineering Manager. Audits architecture, sets up isolated environments, extracts AST repo map, and creates atomic plans.
Phase 1. Act as the strategic visionary and brainstormer. Integrates /office-hours and brainstorming rules.
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Fast-track composite skill that chains CEO, Design, and Engineering reviews automatically, dumping a final spec and AST context.
The execution engine. Merges subagent-driven-development, executing-plans, and test-driven-development into a ruthless coding machine.
The diagnostic clinic. Mashing /investigate and systematic-debugging. Blocks naive code patching without evidence.