메뉴
Reference stub pointing to using-skills and vibe auto. The pipeline's operational logic now lives in `vibe` (runtime) and `using-skills` (routing + decision principles). Triggers: "workflow", "pipeline", "what runs at which stage".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Turn a fuzzy idea into a concrete, reviewable spec via structured dialogue. THINK stage entry. Triggers: "brainstorm", "design", "spec this out", "let's think through".
Multi-lens auto-review of an IMPLEMENTATION PLAN (not code). Strategy → Design (if UI) → Engineering phases. All decisions auto-resolved via 6 Decision Principles. Triggers: "review plan", "autoplan".
Post-ship documentation update. Cross-references the diff, updates README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md to match what shipped. Polishes CHANGELOG voice, cleans up TODOs, optionally bumps VERSION. Triggers: "update docs", "sync documentation", "post-ship docs", "update the readme", "document what shipped". Proactively suggest after a PR is merged or code is shipped.
Meta-skill: create, install, list, and manage skills and agents within the superomni framework. Merges writing-skills + agent-management into one unified workflow. Triggers: "create skill", "write a skill", "install skill", "list skills", "create agent", "write an agent", "install agent", "list agents", "new skill", "new agent", "add skill", "add agent", "manage framework".
Combined RELEASE stage (ship + retrospective) in a single artifact. Triggers: "/release", "end sprint", "ship and reflect". Replaces the retired ship skill.
Use when turning a spec or idea into a concrete, executable implementation plan. Triggers: "write a plan", "plan this out", "create implementation plan", "how should we implement".
| name | workflow |
| description | Reference stub pointing to using-skills and vibe auto. The pipeline's operational logic now lives in `vibe` (runtime) and `using-skills` (routing + decision principles). Triggers: "workflow", "pipeline", "what runs at which stage". |
| allowed-tools | ["Read"] |
| when_to_use | Use as a quick lookup when you need to remember which skill runs at which stage or what artifact each stage produces. For running the pipeline, use `vibe auto` (or plain `/vibe`). |
| produces | null |
| consumes | null |
Status protocol — end every session with one of: DONE (evidence provided) · DONE_WITH_CONCERNS (list each) · BLOCKED (state what blocks you) · NEEDS_CONTEXT (state what you need).
Auto-advance — pipeline: THINK → PLAN → REVIEW → BUILD → VERIFY → RELEASE. Only human gate is spec approval at THINK. On DONE at other stages, print [STAGE] DONE -> advancing to [NEXT-STAGE] and invoke the next skill. On any non-DONE status at any stage, STOP.
Output directory — all artifacts go in docs/superomni/<kind>/<kind>-[branch]-[session]-[date].md. See CLAUDE.md for the full directory map.
TACIT-DENSE — before high-tacit decisions, classify D1 (domain expertise) · D2 (user-facing UX) · D3 (team culture) · D4 (novel pattern). On hit, output TACIT-DENSE [D#]: [question] — My default: [recommendation]. See reference for actions.
Anti-sycophancy — take a position on every significant question. Name flaws directly. No filler ("that's interesting", "you might consider", "that could work").
Telemetry (local only) — at session end, log bin/analytics-log. Nothing leaves the machine.
See preamble-ref.md for detailed protocols.
Static pointer. Operational pipeline logic lives in vibe (runtime) and using-skills (routing).
THINK → PLAN → REVIEW → BUILD → VERIFY → RELEASE
| Question | Answer |
|---|---|
| Run the pipeline end-to-end | /vibe auto |
| Run step-by-step | plain /vibe |
| Which skill handles each stage | using-skills Quick Reference + skills/vibe/SKILL.md |
| Artifact each stage produces | Skill frontmatter produces: + CLAUDE.md output convention |
| Validate artifact contract | npm run check:workflow-contract |
Status: DONE
