claude-swe-workflows: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Overview

This is claude-swe-workflows, a Claude Code plugin for software engineering workflows. It provides skills and agents that extend Claude Code's capabilities for systematic development.

Plugin Structure

├── .claude-plugin/
│   ├── marketplace.json # Marketplace manifest (lists plugins for installation)
│   └── plugin.json      # Plugin metadata (name, version, description, license)
├── agents/              # Agent definitions
│   └── agent-name.md    # Agent prompt with YAML frontmatter
├── skills/              # Skill definitions
│   └── skill-name/
│       ├── SKILL.md          # Skill prompt with YAML frontmatter
│       └── references/
│           └── README.md     # Human-readable guide for the skill
├── references/          # Cross-cutting reference and discipline docs
│   ├── autonomy.md          # Discipline for the orchestrator namespaces
│   ├── think.md             # Design discipline for the /think-* namespace
│   └── ...
├── CHANGELOG.md
├── CONTRIBUTING.md
└── README.md

Development

Test the plugin locally:

claude --plugin-dir .

Writing Skills and Agents

Skills (in skills/*/SKILL.md):

• YAML frontmatter: name, description, model (opus/sonnet/haiku - lowercase)
• Invoked by user with /skill-name
• Define workflows, processes, or specialized behaviors

Agents (in agents/*.md):

• YAML frontmatter: name, description, model (lowercase)
• Spawned programmatically via Task tool with subagent_type
• Operate autonomously within defined scope

Model names must be lowercase (opus, sonnet, haiku) - capitalized names are not recognized.

New /think-* skills must pass the five tests in references/think.md. When proposing or designing a new /think-* skill, read references/think.md first and check the proposal against the tests there. Skills outside the /think-* namespace are admitted by different criteria — primarily, whether they earn their keep in real software-engineering work — though the practitioner-methodology and structured-discipline values described in references/think.md apply across the plugin.