A structured development workflow for Claude Code that turns ideas into working software, one phase at a time. Includes a Claude Code plugin (simply/) and Jujutsu workspace tooling for parallel feature development.

The core of this project is a Claude Code plugin that guides you through a repeatable development loop:

idea --> design --> plan --> next --> (work) --> commit
  ^                                    |
  +------------------------------------+

1. Capture ideas as they come (/simply:idea)
2. Design solutions collaboratively (/simply:design)
3. Plan approved designs into tasks (/simply:plan)
4. Work on tasks one at a time (/simply:next)
5. Commit changes atomically (/simply:commit)
6. Repeat

Each project managed by Simply maintains a structured documentation tree:

docs/
├── PROJECT.md               # Project context + architecture + frontmatter
└── {project}/
    └── {version}/
        ├── IDEAS.md         # Idea inbox (lifecycle-tracked)
        ├── DESIGN.md        # Design documents
        ├── ROADMAP.md       # Feature roadmap
        ├── TASKS.md         # Flat task backlog (all phases, Phase column)
        └── journals/
            ├── 01.md        # Phase 01 journal
            ├── 02-auth.md   # Phases can have names, not just numbers
            └── polish.md

Phase is a label, not a container. Tasks live in one flat TASKS.md (Phase column + global T{N} IDs) so you get a single overview of all open work. Journals stay bounded per phase in journals/{phase}.md. Phase identifiers are freeform strings — number (01), name (polish), or mixed (02-auth).

docs/PROJECT.md is auto-loaded into every session via a SessionStart hook. It carries the current workflow state in frontmatter (project / version / phase) plus the project's problem statement, current focus, and Architecture section — so Claude has intent + codebase bootstrap for free on every session, with no per-command scanning.

• One thing at a time: Focus on the current task
• PROJECT.md is the bootstrap: One file, auto-loaded, covers intent + architecture
• Checkpoint often: Save progress incrementally
• Atomic commits: Each commit is one coherent change; commits also journal and refresh the Architecture section when structural changes happen
• Carry context forward: Phase transitions auto-prepend a recap to the next phase's JOURNAL.md

# Install the plugin
./simply/setup.sh

# Initialize a project
/simply:next

The repository also includes shell-based workspace management for Jujutsu (jj), providing Git-like branch workflows using jj workspaces with color-coded VSCode windows.

• Isolated Workspaces: Separate working directories per feature
• Color-Coded VSCode Windows: Unique color theme per workspace
• Selective Merging: Merge all commits or cherry-pick specific ones
• Linear History: Rebase-based workflow for clean commit history

Add VSCode terminal integration to your shell RC file (.bashrc or .zshrc):

# VSCode terminal integration - load workflow tools
if [ "$TERM_PROGRAM" = "vscode" ]; then
    source /path/to/workflow/etc/shell-init.zsh  # or .bash
    register_tools "/path/to/workflow"
    register_tools "$(pwd)"
fi

workflow init              # Initialize jj in a git repo
workflow create my-feature # Create a new feature workspace
jj commit -m "Add feature" # Work and commit
workflow merge my-feature  # Merge into main
jj git push                # Push to remote
workflow delete my-feature # Clean up

MIT License - feel free to use and modify for your needs.