organize

Organize

Map the stages and flow of the framework.

Inputs

Input	Source
framework_charter	Frame stage output
stages	User input
pattern	User input
feedback_loops	User input
reference_frameworks	Optional

Input Format

From Frame stage (output/{date}/{name}/1-frame/charter.md):

# Framework Charter: {NAME}

## Problem
{Workflow being addressed}

## Purpose
{Why this framework exists}

## Scope
**In:** {What's covered}
**Out:** {What's excluded}

## Type
{Foundation / Pipeline / Cyclical / Hub}

## Dependencies
| Requires | From | Why |

Optional reference frameworks:

reference_frameworks:
  - path: docs/models/[framework].md

Process

1. Identify Stages - Break the workflow into distinct stages:

• What are the major phases of work?
• Each stage should have a clear purpose and output
• Aim for 3-7 stages (fewer for foundation frameworks)

2. Name Stages - Choose clear, action-oriented names:

• Verbs or nouns that describe what happens
• Consider acronym potential if desired
• Check for naming conflicts with existing skills

3. Map Flow - Determine how stages connect:

• Linear: A → B → C
• Branching: A → B or C based on condition
• Hub: Central stage others connect to
• Draw the flow as a mermaid diagram

4. Define Dependencies - What does this framework need from others:

• Which inputs come from other frameworks?
• At which stage are they needed?

5. Identify Feedback Loops - When to go backwards:

• What conditions cause a return to earlier stages?
• What triggers re-evaluation?

6. Define Terminal States - How does the framework end:

• Success state(s)
• Failure/exit states
• What actions accompany each?

Interaction

Use the AskUserQuestion tool for:

• Confirming stage names and purposes
• Choosing between flow patterns (linear, branching, hub)
• Identifying feedback loop conditions

Always use AskUserQuestion (not plain text) when gathering input, clarifying requirements, or requesting approval.