| 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:
- Workflow playbook: ../../../../.looply/state/workflow-playbook.opencode.md
- Command index: ../../../../LOOPLY_COMMANDS.md
- Host contract: ../../../../HOST_CONTRACT.md
- Host status contract: ../../../../.looply/state/host-status-contract.json
- Project contract: ../../../AGENTS.md
When to use:
- The user does not know which looply workflow to start.
- The user asks how to continue a feature.
- The user wants the available looply workflows.
- The user asks for help with looply in Codex.
Behavior:
- If the user asks what Looply can do, list the available workflows and when to use each one.
- If the user describes a raw idea, recommend
idea-to-prd.
- If the user already has a PRD, recommend
prd-to-stories.
- If the user already has a story and wants to implement, recommend
story-to-production.
- If the user needs cloud topology, async-first trade-offs, governance or workload cost direction, recommend
cloud-workload-design.
- If the user needs shared platform baselines, guardrails, pipelines or foundation evolution, recommend
platform-foundation-evolution.
- If the user wants to know where work stopped, recommend
workflow-status, resume or next.
- If the user asks for host-driven autonomy, consult
HOST_CONTRACT.md, host-status-contract.json and use looply autonomy <feature> to derive the next cycle.
- Before routing to a specialist, inspect the agent
knowledge_sources, especially specialist best-practices files.
- If the current task declares templates or checklists, treat them as the default artifact contract and quality bar.
- When curated examples are referenced by a workflow command, treat them as style guidance only.
- Prefer explicit next-step guidance over generic explanations.
- Respond in the same language as the user's input.
- Respect project mode existing-project and interaction mode balanced.
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 workflow
Recommended 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:
- Use clear Markdown section titles.
- Prefer concise recommendations.
- Do not use emojis.
