oc-stack-forge

Topics in the source

• Stack Forge
• How This Skill Fits the Build Pipeline
• /oc-stack — Command Reference
• Stack Decision Tree (/oc-stack-decide)
• How It Works
• Question 1: Platform & Hosting
• Question 2: Backend Language & Framework
• Question 3: Database

On first invocation, read references/orchestrator.md and follow its welcome protocol. Opinionated stack advisor that helps you pick the right tools and enforces type safety across whatever stack you choose. Invoked as an explicit Phase 2 step by oc-app-architect — you don't call it separately for new projects. Works with any stack: Cloudflare Workers, Vercel/Next.js, AWS Lambda, Supabase, Rails, Django, Go, Rust — the decision framework is universal. The implementation patterns are stack-specific, loaded from reference docs at runtime. App-architect invokes oc-stack-forge as a Phase 2 step (orchestrator.md §3 — a step it runs, not an automatic trigger). Its recommendation feeds 01-tech-stack.md and 02-architecture.md, so the user doesn't need to call /oc-stack separately for a new project. Stack-forge reads the discovery interview results and recommends the best stack for the project's requirements. /oc-feature gives a stack-ordered decomposition of a feature, regardless of stack choice, that the user can bring into a sprint plan (for example oc-app-architect's /oc-roadmap). oc-app-architect does not call it on its own. -- Comparing two or three specific stack options side by side

This is an excerpt. Refer to the complete source and its current requirements.