| name | looply-sessions |
| description | Use to list, inspect or manage linked looply sessions from chat. Shows session details and resume commands. |
Use this skill when the user explicitly invokes $looply-sessions, asks to run /looply:sessions, or requests session management actions (list sessions, show a session, or remove a session).
Workflow phase: none.
Category: navigation.
Quick usage:
$looply-sessions [action] [args]- Actions:
list, show <label>, unlink <label>
Primary references:
- Session links: ../../../../.looply/custom/session-links.json
- Session context: ../../../../.looply/custom/session-context.md
- CLI command:
looply sessions
- Managed pack: ../../../../.looply/managed/packs/software-delivery-suite
- Custom overrides: ../../../../.looply/custom
Usage:
- Explicit mention:
$looply-sessions
- Workflow alias to honor:
/looply:sessions and $looply-sessions depending on host
- Syntax in OpenCode:
$looply-sessions [list|show <label>|unlink <label>]
Example:
- $looply-sessions list
- $looply-sessions show backend-afternoon
- $looply-sessions unlink old-session
When to use:
- The user wants to see all linked sessions and their features.
- The user wants details about a specific session.
- The user wants to remove a session link.
- If no action is specified, default to
list.
Curated example guidance:
- ICL mode:
on
- Use examples only for style, structure and quality calibration.
- Do not copy feature-specific names, identifiers or business details from examples.
- No example was selected for this workflow.
Execution rules:
- Read
.looply/custom/session-links.json to inspect current sessions.
- If no action specified, default to listing all sessions.
- For
list action: display all linked sessions with label, feature, workflow, last command, and updated timestamp.
- For
show <label> action: display full session details and the resume command to paste in a new chat tab.
- For
unlink <label> action: confirm with the user before removing, then remove the session.
- If the user asked for help, explain syntax, arguments, example, expected output and next step without mutating state.
- Do not modify managed pack files. Write local state only under
.looply/custom.
- Respond in the same language as the user's input.
- Keep the response visually structured with clear Markdown section titles.
- Do not use emojis.
Composed Agent Context
The sections below were pre-composed by looply from agent context_slots.
Constraints
- Do not implement feature code directly
- Do not modify managed pack files
- Do not remove sessions without explicit user confirmation
Escalation
- Escalate missing features to
$looply-workflow-status
- Escalate feature creation to
$looply-idea-to-prd
Project Rules
project-conventions
Project Conventions
Purpose
Define project-level conventions for collaboration that agents must follow when interacting with version control, pull requests and releases.
Rules
- Follow the project's established branching strategy.
- Write clear, descriptive commit messages.
- PRs must include a summary of changes and link to the relevant story.
- Do not commit generated files or build artifacts.
- Changes that affect multiple concerns should be split into separate PRs.
Examples
- Good commit:
feat: add retry logic to payment processing
- Bad commit:
fix stuff
Enforcement
- Branch protection rules enforce review requirements.
- CI checks run on every PR.
- Commit message convention enforced via hooks or CI.
Arguments:
- action: list, show , or unlink (optional, defaults to list)
- label: session label for show or unlink actions
