build-productionos

Route natural-language intents to the correct ProductionOS workflow.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill build-productionos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-productionos
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/build-productionos
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill build-productionos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ProductionOS needs a simple, universal entry point to route user intents to the correct workflow, reducing the learning surface for new users and ensuring consistent routing across tasks.

Core Features & Use Cases

  • Single-entry routing: directs natural language intents to the appropriate ProductionOS workflow (audit, design, fix, plan, build, etc.) for automated orchestration.
  • Static + smart routing: combines keyword-based routing with optional agent-informed routing to choose the right command and tailor tool provisioning.
  • Stack-aware execution: detects project stacks to inform tooling and optimize the workflow path for codebases of varying tech stacks.

Quick Start

Ask it to route an intent, for example 'audit this project', to begin the appropriate ProductionOS workflow.

Frequently Asked Questions about build-productionos

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

FAQPage Schema
How do I route natural language intents to the correct development workflow?

Natural language intents are routed to the correct development workflow by classifying the input text and directing it to the corresponding command. This handles scenarios like audit, design, fix, plan, build, debug, test, review, and ship.

What is the best way to automate task orchestration across different software engineering scenarios?

Automating task orchestration is achieved through a multi-step sequence including preamble, agent indexing, optional stack detection, and static fallback routing. This ensures reliable execution and direct routing to the appropriate workflow.

How does stack detection work for routing codebase tasks to the right workflow command?

Stack detection works by identifying the project stacks within a codebase to inform tooling choices. This optimizes the workflow path and tailors tool provisioning for codebases of varying tech stacks.

Can I use a single entry point to trigger automated workflows for fixing and debugging code?

Yes, a single-entry routing system directs intents to appropriate automated workflows for fixing and debugging code. It combines keyword-based static routing with optional agent-informed routing to choose the right command.

When should I use static fallback routing for workflow automation?

Static fallback routing is used when initial agent-informed routing cannot definitively classify an intent. It ensures every request still reaches a valid workflow command, maintaining reliable execution across all supported scenarios.