structure
/structure
Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.
- Author
- alirezarezvani ↗
- Repository
- gaios ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.
Triggers from the description
Original author description
Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.
How it works
- When to run
- The output (always this shape)
- Process
- Guardrails (from CLAUDE.md)
SKILL.md preview
---
name: structure
description: Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.
---
# Structuring Engine
A common leverage point: inputs arrive **without structured context, defined outcomes, or clear goals.** This skill fixes that before any work begins. Frame first, then act (or delegate).
## When to run
- A new task lands fuzzy ("the boss wants the draft checked", "look into the X thing").
- A long email/chat thread needs to become an action.
- The user is about to do something the old way → apply the **Default Shift** ("to what extent could AI be leveraged here?").
## The output (always this shape)
```
## <short title>
**Context** — what's going on, in 2-4 plain sentences. The why behind the ask.
**Desired outcome** — the end state. What does "done" look like, concretely?
**Goal** — the measurable/observable target (a date, a number, a deliverable). One line.
**Owner** — who should own this (route to the team; don't pool on the user by default).
**Next step** — the single next physical action, and by when.
**Decision needed** — the specific call the user must make, framed as a fast choice.
```
When a decision is involved, present it as a **fast checklist** they can answer in seconds:
```
- Send to the client now (yes/no)?
- Loop in <reviewer> first (yes/no)?
- Target date: <propose one>
```
## Process
1. **Read everything given.** If it references a ticket, doc, or thread and a connection exists, pull it rather than guessing.
2. **Strip to the real ask.** Separate noise from the actual decision/outcome. Name what's missing.
3. **Fill the template.** Be concrete. If a field is genuinely unknown, write `❓ <the open question> → <who can answer>` instead of inventing.
4. **Route the owner.** Default to delegating to the right teammate; only put the user as owner when it's truly theirs (a decision, an external sign-off).
5. **Offer the next move.** After the brief, offer to: create the artifact (ticket / note / plan — allowed without approval), draft the reply in the user's voice (internal may send to team; never external without approval), and/or log a decision to `decisions/log.md`.
## Guardrails (from CLAUDE.md)
- No confidential figures or sensitive/regulated data persisted to the repo. Pull live, don't store.
- **Cite, don't invent** — any regulatory/financial/legal claim cites a source or is flagged as a gap.
- **Draft, never send external.** Internal to the team may be OK; external needs approval.
- Match `references/voice.md`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alirezarezvani/gaios | 100 | MIT |
| zengtianli/cc-configs | 96 | MIT |
| owl-listener/inclusive-design-skills | 90 | MIT |
| melodic-software/claude-code-plugins | 84 | MIT |
Database snapshot: 13.11.2026 · package version e65eb54839d9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86d2s-frame
Stage 1 (frame) of a discovery-to-spec design exploration. Turns a feature request, idea or stakeholder ask into a one-page brief covering the problem, who it matters to, where it lives in the product today, the desired outcome, the appetite and the no-gos. Use whenever someone… - 100prd-from-idea
Turn a raw product idea — a paragraph, a Notion dump, a half-formed thought, or a brief that arrived as a **file** (`.docx`, `.pdf`, `.pptx`, `.xlsx`: an RFP, a client deck, a Word spec — converted to Markdown first with `anydoc`) — into a structured PROJECT.md (high-level… - 100pm-spec-writing
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear… - 100grilling-ideas
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO… - 100workflow-refine
Turn rough user input into an autonomy-ready brief. Use when the user describes work that is vague, incomplete, or needs clarification before it can become a workflow packet. Asks clarifying questions, proposes concrete options, and produces a structured brief for workflow-create. - 95create-brief
Use this skill when the user says 'I want to build', 'new app idea', 'create a brief', 'product brief', 'help me define what I am building', or when no existing brief or PRD exists in the docs/ folder. This skill translates a vague idea into a structured Product Brief. It asks 5…