Knowledge Vault

Gloriously Awesome System

2 min read

Overview

The Gloriously Awesome System (GAS) is a meta-prompting, context engineering, and spec-driven development system for Claude Code, forked from GSD (Get Shit Done) by TACHES. It manages Claude Code’s context window deliberately through structured XML plans, subagent orchestration, and fresh context per task — optimizing for a solo developer + Claude workflow with no enterprise patterns. GAS operates as a set of commands and workflows that coordinate planning, execution, and verification, with 14 specialized subagents that each run in fresh 200k-token contexts to prevent quality degradation. The system has zero runtime dependencies: pure JavaScript (ES2020+) running via the Claude Code plugin API, installable via npx gloriously-awesome-system-cc.

Key Concepts

  • Command structure — Commands (commands/gas/*.md) are orchestrators targeting under 150 lines, delegating logic to workflows (gloriously-awesome-system/workflows/*.md). Templates define output structure; references provide deep-dive principles.
  • Subagent system — 14 agents handle execution, verification, research, debugging, codebase mapping, and milestone auditing. Each runs in isolated fresh context to avoid quality degradation from accumulated state.
  • State files — PROJECT.md, ROADMAP.md, STATE.md, PLAN.md, SUMMARY.md, ISSUES.md are managed in a .planning/ directory within target projects. These files are the ground truth for session continuity.
  • XML for plans — PLAN.md files use structured XML as executable prompts, not documentation. Plans are limited to 2-3 tasks maximum to maintain context quality.
  • Atomic commits — Format: {type}({phase}-{plan}): {description}. Files are staged individually — never git add . or git add -A.
  • Key commands — /gas:new-project extracts ideas, /gas:create-roadmap generates ROADMAP.md and STATE.md, /gas:execute-phase runs subagent orchestration, /gas:verify-work performs user acceptance testing, /gas:pause-work and /gas:resume-work handle session handoffs.
  • Gas-manifest.json — Tracks critical files and orphans for installation integrity verification. Must be updated after modifying critical files.
  • AP Ecosystem — The ecosystem GAS is built to serve
  • Ops-Core — Governance layer that GAS sessions must comply with
  • Multi-Agent Workflow — GAS subagents are a key component of multi-agent coordination
  • Context Windows — The finite memory constraint that GAS is explicitly designed to manage

Graph View

Backlinks