Attune

Full-cycle project development from ideation to implementation.

Overview

Attune integrates the brainstorm-plan-execute workflow from superpowers with spec-driven development from spec-kit to provide a complete project lifecycle.

Workflow

graph LR
    A[Brainstorm] --> B[War Room]
    B --> C[Specify]
    C --> D[Plan]
    D --> E[Initialize]
    E --> F[Execute]

    style A fill:#e1f5fe
    style B fill:#fff9c4
    style C fill:#f3e5f5
    style D fill:#fff3e0
    style E fill:#e8f5e8
    style F fill:#fce4ec

Commands

Supported Languages

• Python: uv, pytest, ruff, mypy, pre-commit
• Rust: cargo, clippy, rustfmt, CI workflows
• TypeScript/React: npm/pnpm/yarn, vite, jest, eslint, prettier

What Gets Configured

• Git initialization with detailed .gitignore
• ✅ GitHub Actions workflows (test, lint, typecheck, publish)
• ✅ Pre-commit hooks (formatting, linting, security)
• ✅ Makefile with standard development targets
• ✅ Dependency management (uv/cargo/package managers)
• ✅ Project structure (src/, tests/, README.md)

Quick Start

New Python Project

# Interactive mode
/attune:init

# Non-interactive
/attune:init --lang python --name my-project --author "Your Name"

Full Cycle Workflow

# 1. Brainstorm the idea
/attune:brainstorm

# 2. War room deliberation (auto-routes by complexity)
/attune:war-room --from-brainstorm

# 3. Create specification
/attune:specify

# 4. Plan architecture
/attune:blueprint

# 5. Initialize project
/attune:init

# 6. Execute implementation
/attune:execute

Skills

Agents

Integration

Attune combines capabilities from:

• superpowers: Brainstorming, planning, execution workflows
• spec-kit: Specification-driven development
• abstract: Plugin and skill authoring for plugin projects

Interactive Plan Review

When transitioning from planning to execution, the mission orchestrator presents the generated plan for user review. The review loop supports three verdicts:

• approve: Accept the plan and proceed to execution.
• revise: Provide feedback; the planner regenerates with your revision context injected.
• reject: Abandon the plan and return to an earlier phase.

Plan revisions are versioned with diffs between iterations. An iteration governor caps revisions at 3 rounds to prevent unbounded cycles. If the cap is reached, the user chooses between approving the current version or rejecting outright.

War Room Integration

The war room is a mandatory phase after brainstorming. It automatically routes to the appropriate deliberation intensity based on Reversibility Score (RS):

The war room includes a Prosecution Counsel role that stress-tests proposals by probing failure modes, hidden costs, and unstated assumptions before the panel votes.

The war-room-checkpoint skill can also trigger additional deliberation during planning or execution when high-stakes decisions arise.

Discussion Publishing

After the Supreme Commander synthesis (Phase 7), the war room offers to publish the decision to a GitHub Discussion in the “Decisions” category. This requires user approval and checks for prior decisions on the same topic to avoid duplicates. The published Discussion includes the full decision record with alternatives considered, scoring breakdown, and implementation guidance. Local strategeion files remain the primary record; the Discussion is an additional cross-session discovery channel.

Examples

Initialize Python CLI Project

/attune:init --lang python --type cli

Creates:

• pyproject.toml with uv configuration
• Makefile with test/lint/format targets
• GitHub Actions workflows
• Pre-commit hooks for ruff and mypy
• Basic CLI structure

Upgrade Existing Project

# Add missing configs
/attune:upgrade-project

# Validate structure
/attune:validate

Configuration

Custom Templates

Place custom templates in:

• ~/.claude/attune/templates/ (user-level)
• .attune/templates/ (project-level)
• $ATTUNE_TEMPLATES_PATH (environment variable)

Reference Projects

Templates sync from reference projects:

• simple-resume (Python)
• skrills (multi-language)
• importobot (automation)