Skip to content

Skills Overview

OpenLogos ships with 18 AI Skills — structured Markdown instruction files (SKILL.md) that guide AI coding tools through each phase of the development lifecycle. Skills are deployed automatically during openlogos init and synchronized via openlogos sync.

Each Skill is a self-contained instruction set stored in skills/<skill-name>/SKILL.md. When an AI coding tool encounters a task matching a Skill’s trigger conditions, it reads and follows the instructions to produce consistent, high-quality outputs.

Skills are organized to follow the OpenLogos three-layer progression model (WHY → WHAT → HOW):

SkillPurposeTrigger
project-initInitialize project structure and configurationNew project setup or openlogos init
prd-writerWrite scenario-driven requirements with GIVEN/WHEN/THEN criteriaRequirements analysis phase
SkillPurposeTrigger
product-designerCreate interaction specs and prototypes adapted to product typeRequirements exist, design needed

Phase 3 — HOW (Technical Implementation)

Section titled “Phase 3 — HOW (Technical Implementation)”
SkillPurposeTrigger
architecture-designerDesign system architecture and select technology stackProduct design complete, Step 0
scenario-architectExpand scenarios into technical sequence diagramsArchitecture complete, Step 1
api-designerDesign OpenAPI specs derived from sequence diagramsSequence diagrams complete, Step 2
db-designerDerive database DDL from API specificationsAPI specs complete, Step 2
test-writerDesign unit test and scenario test casesSpecs complete, Step 4a (all projects)
test-orchestratorDesign API orchestration test scenariosTest cases complete, Step 4b (API projects only)
code-implementorGenerate business code and test code with spec fidelityTest design complete, Step 5
code-reviewerReview code against the full specification chainAfter code generation, Step 5+
SkillPurposeTrigger
deployment-designerDesign deployment topology, release commands, rollback strategy, and smoke scopeAPI/DB complete, Step 3
deployment-executorExecute deployment with human authorization after verify passesAfter Gate 3.6 PASS, Step 7
SkillPurposeTrigger
change-writerWrite change proposals with impact analysisAny iteration during launched lifecycle
slice-plannerPlan post-spec-complete [code] slices from merged specs and real test IDsAfter merge / no-delta spec-complete, before code implementation
merge-executorMerge delta files into main documentsAfter openlogos merge <slug>
SkillPurposeTrigger
brownfield-adopterOptional: reverse-engineer a verifiable baseline seed (system map + scenario candidates) from an existing codebase and commit it with openlogos baseline-seedOnly when you explicitly ask for an up-front full-codebase scan; never triggered just because openlogos adopt finished
SkillPurposeTrigger
ui-ux-pro-maxComprehensive UI/UX design guide (67 styles, 96 palettes, 57 font pairings, 25 chart types)GUI product design in Phase 2, invoked by product-designer

After openlogos init, Skills are deployed to platform-specific locations:

AI ToolSkill Location
Claude Codelogos/skills/ (native plugin)
OpenCodelogos/skills/ (hooks integration)
Codex.agents/plugins/openlogos/skills/ ($openlogos:<skill> native Codex Skills)
Cursor.cursor/skills/<name>/SKILL.md (native Agent Skills)
ZCode.zcode/plugins/openlogos/skills/ (native plugin)
Qoder.qoder/plugins/openlogos/skills/ (native plugin)
WorkBuddy.workbuddy/plugins/openlogos/skills/ (native plugin)
Otherlogos/skills/

Multi-file Skill assets (such as ui-ux-pro-max) always stay under logos/skills/. Run openlogos sync to re-deploy Skills after updates. See init for the full list of files each host receives.