Menu
Use when the user asks what looply can do, how to start a workflow, which workflow to use, or how to continue a feature in Codex.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use to list, inspect or manage linked looply sessions from chat. Shows session details and resume commands.
Use to open a new session tab for a feature. Registers the session in session-links.json and provides the resume command for the new tab.
Use to review architecture and design independently. Identifies structural improvements, validates against existing ADRs, and verifies compliance with codebase design principles.
Use to execute structured code review like GitHub and CodeRabbit. Reviews code changes, classifies findings by severity and generates actionable suggestions. Formal delivery gate with approval checklist.
Use to prepare and validate a software release. Includes security, performance, monitoring, rollback and operability checklist. Final delivery gate before production deploy.
Use when a delivery story already exists and needs technical design, implementation, review and release preparation. Do not use before discovery and planning are complete.
| name | looply |
| description | Use when the user asks what looply can do, how to start a workflow, which workflow to use, or how to continue a feature in Codex. |
Use this skill as the main entrypoint for Looply inside Codex.
Primary references:
When to use:
Behavior:
idea-to-prd.prd-to-stories.story-to-production.cloud-workload-design.platform-foundation-evolution.workflow-status, resume or next.HOST_CONTRACT.md, host-status-contract.json and use looply autonomy <feature> to derive the next cycle.knowledge_sources, especially specialist best-practices files.Available workflows:
$looply-cloud-workload-design <feature-name> <scope-reference> [constraints...]
Define cloud topology, governance controls and cost posture for a workload change$looply-idea-to-prd <feature-name> [problem-statement] [constraints...]
Start discovery and consolidate an idea into an approved PRD$looply-next <feature-name> [session-label] [notes...]
Show the next recommended step for the current feature workflow$looply-platform-foundation-evolution <initiative-name> [constraints...]
Evolve shared platform foundation with guardrails, governance and cost review$looply-prd-to-stories <feature-name> [prd-reference] [notes...]
Break an approved PRD into delivery-ready stories$looply-resume <feature-name> [session-label] [notes...]
Resume the current feature workflow from the persisted state$looply-story-to-production <feature-name> <story-reference> [constraints...]
Execute delivery for a single approved story until release planning$looply-workflow-status <feature-name> [session-label] [notes...]
Inspect or resume the current status of a looply feature workflowRecommended sequence:
$looply-idea-to-prd <feature-name> [problem-statement] [constraints...]$looply-prd-to-stories <feature-name> [prd-reference] [notes...]$looply-story-to-production <feature-name> <story-reference> [constraints...]$looply-cloud-workload-design <feature-name> <scope-reference> [constraints...] when cloud topology, async-first or governance is the main problem$looply-platform-foundation-evolution <initiative-name> [constraints...] when shared platform baseline or guardrails are the main problem$looply-workflow-status <feature-name> [notes...]Presentation rules: