om-cto

Analyze platform gaps and orchestrate spec writing for Open Mercato.

6|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/SHGrowth/om-superpowers --skill om-cto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-cto
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-cto
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-cto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Piotr's CTO-focused guidance helps Open Mercato teams identify platform gaps, steer architecture decisions, and orchestrate end-to-end spec-writing and implementation workflows across advisory, spec orchestration, and implementation phases.

Core Features & Use Cases

  • Gap analysis and architecture direction: determines whether OM covers a requirement or needs UMES extension.
  • Spec orchestration: decomposes app specs into functional specs and oversees their implementation.
  • Mode detection and guidance: routes conversations to advisory, spec orchestrator, or implementation orchestrator.
  • Reference-driven decisions: loads Piotr's decision patterns from the decision library to guide choices.
  • Use case handling: responds to questions like "does OM already do X?", "write specs from app spec", or "implement approved specs" and drives the appropriate flow.

Quick Start

Describe a project goal and have Piotr perform gap analysis to determine the next steps for architecture, spec writing, or implementation.

Frequently Asked Questions about om-cto

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

FAQPage Schema
How do I perform platform gap analysis for Open Mercato?

To perform platform gap analysis for Open Mercato, describe a project goal to determine if OM covers the requirement or needs a UMES extension, then route the workflow to architecture, spec writing, or implementation.

What is the best way to orchestrate spec writing from an app spec?

Spec orchestration decomposes an app spec into functional specs, oversees their implementation, and documents decision patterns and mechanisms for traceability from advisory to deployment.

How does UMES extension architecture work in Open Mercato?

UMES extension architecture in Open Mercato provides adapters and decision patterns that document mechanisms for traceability, extending platform capabilities when gap analysis identifies missing coverage.

Can I implement approved functional specs directly through architecture orchestration?

Yes, you can implement approved specs by detecting the implementation orchestrator mode, which drives the execution flow while documenting decisions and mechanisms for traceability from advisory to deployment.

When do I need architecture decision patterns for Open Mercato extensions?

You need architecture decision patterns when performing platform gap analysis that requires UMES extensions, ensuring choices are loaded from the decision library to guide implementation and maintain traceability.

Does Open Mercato gap analysis support standalone architecture questions?

Yes, the gap analysis applies to standalone architecture questions alongside tasks like checking if OM already does a specific feature, writing specs from app specs, or implementing approved specs.