aug

Aug Plugin Marketplace

Workflow patterns and development standards for Claude Code.

What is Aug?

Aug is a collection of workflow patterns for software development with Claude Code. It provides:

• Epic planning workflows - idea → architecture → tasks → implementation
• Maturity models - progressive capability addition with YAGNI
• Quality automation - coverage, complexity, and security gates
• Development standards - justfile interface, stack configurations

The Foundation: Code Quality First

The tools don't matter nearly as much as the quality of the codebase you're developing in.

There's nothing magic about Aug. These workflows only work because they assume a high-quality codebase with:

• Comprehensive test coverage (96% threshold)
• Automated quality gates (format, lint, typecheck, coverage)
• Clear documentation (CLAUDE.md files for AI context)
• Consistent patterns (one way to do things)

The justfile commands, the opinionated stack configurations, the maturity model—all of that exists to establish and maintain this foundation. The first thing I do in any project is tidy up: get quality gates in place, fix existing issues, establish patterns. That's hands-on, intensive work.

Once you have that foundation, autonomous execution becomes reliable. Without it, no amount of clever tooling will help. And with it, many different approaches to AI-assisted development would work well—Aug is just one way.

Why I'm Sharing This

I built these tools for myself, not as a polished reusable framework. They're the workflows I use every day for my own projects. As I've talked to more people about how I work with Claude Code, I realized these patterns have value worth sharing.

This is provided as-is. I welcome input and might accept pull requests, but I'm not trying to build a community project or promote widespread adoption. I'm open-sourcing it so I can share it with people who've asked, and hopefully the ideas are useful. That said, if this stack works great for you, I won't be surprised—this is literally how I work all day, every day.

Opinionated: Aug makes specific technology choices (uv for Python, pnpm for JavaScript, justfile for builds). These choices work well together but aren't universal.

Adaptable: The workflow patterns transfer to any stack. Swap tools while keeping the structure. See ADAPTATION.md.

Installation

# Add marketplace from GitHub
/plugin marketplace add bryonjacob/aug

# Install all plugins
/plugin install aug-dev@aug aug-core@aug aug-just@aug aug-web@aug

How I Use Aug

The core idea: spend your synchronous time on planning, let the machine execute autonomously.

Epic Planning Workflow

This is where I do all my interactive work with Claude. The goal is to front-load my knowledge and decisions into planning documents, then let autonomous execution handle the implementation.

/plan-chat "Add JWT authentication" — Start an interactive session where we discuss the feature, architecture, and testing approach. This is where I'm putting my knowledge into the system about how things should work. Claude asks questions, proposes approaches, and we converge on a design. Output: planning documents in /tmp/devplan/.

/plan-breakdown — Take the plan and break it into bite-sized tasks. A good task is something a human developer could do in a day or less—that's usually something Claude can do in a few minutes with proper context. Each task becomes a self-contained unit of work.

/plan-create — Create GitHub issues from the breakdown. (Opinionated: I use GitHub issues, but you could adapt to Jira, Linear, or markdown files.) Now I have an epic with trackable tasks.

/work 123 — Take issue #123 and work it autonomously: create branch, implement, test, ensure quality gates pass, create PR. No interaction needed. I review the PR when it's ready.

See WORKFLOWS.md for detailed usage.

Automating Any Command

/automate /command — Run any interactive command autonomously. When the command asks questions, a "user-standin" agent analyzes project context (CLAUDE.md, existing code, config files) and answers on your behalf.

/autocommit 123 124 125 — The full autonomous loop: work the issue, self-review, merge. Useful for grinding through a backlog of well-specified tasks.

Workflow Orchestration

/workflow-run epic-development — Execute a multi-command workflow. Combines /automate with workflow definitions to run entire sequences autonomously.

/workflow-status — Check where you are in a workflow.

Session Management

Claude's auto-compact doesn't always preserve context well. These are a quick-and-dirty alternative:

/notetoself — Save current session context to a temp file (directory-isolated). Use when switching tasks or before a long break.