oc-stack-forge

Automate tech stack and architecture selection for software project planning.

Updated May 15, 2026
One-click install
npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-stack-forge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oc-stack-forge
Source: https://github.com/asfbay-bit/opchain-skills/tree/main/skills/oc-stack-forge
Command: npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-stack-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of choosing the right tech stack and architecture for a project, saving time and reducing errors in the planning phase.

Core Features & Use Cases

  • Tech Stack Decision Tree: Offers a guided decision-making process for selecting the appropriate platform, backend language, database, authentication, and frontend framework.
  • Stack Recommendations: Provides a detailed recommendation for the optimal tech stack based on project requirements and constraints.
  • Feature Decomposition: Breaks down features into stack-ordered sprints for efficient development.
  • Checkpoint Protocol: Ensures session persistence and context continuity across skill invocations.
  • Integration with PM Tools: Integrates with project management tools to document architectural decisions as ADRs (Architectural Decision Records).

Quick Start

Use the oc-stack-forge skill to decide the tech stack for your new project.

Frequently Asked Questions about oc-stack-forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tech stack selection for a new software project?

Automate tech stack selection by using a guided decision tree for platform, backend, database, authentication, and frontend choices based on project constraints. This process yields a detailed stack recommendation and feature decomposition for efficient development.

What is the best way to plan software architecture and document decisions?

Plan software architecture by selecting optimal stacks and frameworks, then document architectural decisions as ADRs. Integrating with project management tools ensures these decisions are recorded for session persistence and context continuity.

How does feature decomposition work during architecture planning?

Feature decomposition breaks down project requirements into stack-ordered sprints. This ensures efficient development sequencing by aligning feature implementation directly with the chosen platform, backend, database, and frontend technologies.

Can I use this for database and authentication planning alongside frontend decisions?

Yes, the architecture planning process explicitly covers database, authentication, frontend framework, and backend language decisions. It applies a checkpoint protocol to maintain context continuity across all these stack selection invocations.

Do I need prior knowledge of frameworks to automate my tech stack decisions?

Yes, selecting the optimal tech stack requires existing knowledge of various stacks and frameworks. The automated decision tree guides your platform and backend choices, but understanding project requirements and constraints is necessary for accurate results.

When should I use an automated decision tree for stack selection instead of manual planning?

Use automated stack selection during the planning phase of software development to save time and reduce errors. It is ideal when you need to coordinate platform, backend, database, auth, and frontend choices into a cohesive architecture.