muleteer

内容来源：README.md（说明文档） · 原始地址 · 查看安装指南

原始内容

# Escapement

**Claude Code plugin for structured development workflows.** Regulated workflow, one tick at a time.

## What This Is

Escapement is an opinionated workflow and Claude Code plugin that provides reusable modules to streamline your development process:

- **meta-workflow:** A prescribed sequential process supported by the plugin modules
- **Skills**: Automated workflow modules (issue setup, commits, PRs, etc.)
- **Hooks**: Session archiving on compaction
- **Agents**: Specialized AI assistants (scratchpad-planner for codebase analysis)
- **Multi-Project Support**: Works across all your repos simultaneously

## Workflow Overview

Escapement guides you from idea to merged code through a structured workflow:

1. **Initialize** (`setup-work`) - Pull GitHub issue → Generate scratchpad plan → Create feature branch
2. **Execute** (`do-work` + `commit-changes`) - Work through scratchpad tasks → Make atomic commits
3. **Review** (`create-pr` + `review-pr`) - Create pull request → Review changes → Merge
4. **Archive** (`archive-work`) - Clean up scratchpad → Preserve session history

![High-level workflow diagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow_high_level.png)

Each phase is handled by specialized skills that activate via natural language or explicit commands.

## Installation

### From Source (Development)

```bash
# Clone the repository
git clone https://github.com/fusupo/escapement.git

# Run Claude Code with the plugin
claude --plugin-dir /path/to/escapement
```

### From Marketplace (Coming Soon)

```bash
# Once published to a marketplace
/plugin install escapement
```

## Usage

### High-Level Workflow

Work proceeds through four phases:

* **Initialize**: establish scope and plan
* **Execute**: implement planned work in small steps
* **Review**: validate and merge changes
* **Archive**: preserve artifacts and session history

The phases are sequential but not strictly linear; refinement can push work backward before execution begins.

### Initialize (`prime-session`, `setup-work`)

The session begins either from an idea or an existing GitHub issue.

If needed, project context is loaded by reading `CLAUDE.md` and related documentation.
An issue is created or fetched, then analyzed to produce a scratchpad plan.

If the issue is too large, it is decomposed into sub-issues.
If assumptions are invalid, the issue may be reworked before proceeding.

A feature branch is created once the plan is acceptable.

Operator involvement is primarily directional: clarifying intent and approving scope.

![Initialize phase subdiagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow_initialize.png)

### Execute (`do-work`, `commit-changes`)

Work is driven by the scratchpad.

Tasks are selected one at a time, implemented, and committed as atomic changes following project conventions.
This loop continues until the scratchpad is complete.

The operator may intervene to adjust task order, clarify intent, or pause execution, but most actions are automated.

![Execute phase subdiagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow_do_work.png)

### Review (`create-pr`, `review-pr`)

A pull request is created with full context from the scratchpad and commit history.

The PR is reviewed.
If changes are requested, work resumes and new commits are added before re-review.

This cycle repeats until the changes are accepted and merged.

Operator involvement is typically focused on decision-making and judgment rather than mechanics.

![Review phase subdiagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow_review.png)

### Archive (`archive-work`, hooks)

After merge, the scratchpad is archived.

Before Claude Code compacts the session, the transcript is saved via the PreCompact hook.
This preserves planning, execution, and review context as durable artifacts.

The session is then considered complete.

![Archive phase subdiagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow_archive.png)

### Full Workflow Map

This diagram shows all phases together, with swimlanes for each skill and the operator.

It illustrates where decisions occur, which actions are automated, and how control moves between skills over the life of a session.

![Full swimlaned workflow diagram](https://github.com/fusupo/muleteer/raw/HEAD/workflow.png)

## Skills

Skills are invoked automatically by Claude Code when relevant, or you can reference them explicitly with the `/escapement:` prefix:

**Natural Language Invocation:**
```bash
# Claude uses the skill automatically based on context
"Setup GitHub issue #42"
"Commit these changes"
"Create a PR for this branch"
```

**Explicit Invocation:**
```bash
/escapement:setup-work
/escapement:commit-changes
/escapement:create-pr
```

### Available Skills

| Skill            | Triggers                            | Purpose                                        |
| ---------------- | ----------------------------------- | ---------------------------------------------- |
| `setup-work`     | "setup issue #X", "start issue #X"  | Fetch issue, create scratchpad, prepare branch |
| `commit-changes` | "commit", "commit these changes"    | Smart commits with conventional format         |
| `create-pr`      | "create a PR", "open pull request"  | Context-aware PR creation                      |
| `review-pr`      | "review PR #X", "check this PR"     | Roadmap-aware code review                      |
| `do-work`        | "start working", "continue work"    | Execute tasks from scratchpad                  |
| `archive-work`   | "archive this work", "clean up"     | Move completed scratchpads to archive          |
| `create-issue`   | "create an issue", "file a bug"     | Ad hoc GitHub issue creation from natural language |
| `stash-artifact` | "stash this script", "save to context" | Save artifacts to context directory         |
| `prime-session`  | "orient me", "what is this project" | Read project docs for context                  |

## Hooks

Escapement includes a **PreCompact hook** that captures your raw session transcript before Claude Code's automatic compaction. The hook copies the JSONL transcript to `SESSION_LOG_{N}.jsonl` in the **project root** — a minimal, reliable preservation step.

The `archive-work` skill later converts these `.jsonl` files to readable markdown (using `scripts/convert-session-log.py`) and moves them to the archive directory.

**Requirements:** `jq` must be installed for the hook to function.

## Agents

Specialized subagents for delegation and deep analysis:

### scratchpad-planner

**Automatically invoked** during `setup-work` (Phase 2) for codebase analysis and implementation planning.

**Capabilities:**
- Reads project's CLAUDE.md for conventions and structure
- Analyzes codebase using Grep, LSP, and code search patterns
- Identifies affected modules and integration points
- Finds similar implementations to learn from
- Generates atomic task breakdowns following project conventions
- Asks clarifying questions for ambiguous requirements
- Supports resumable analysis for complex codebases

**Benefits:**
- **Specialized expertise**: Replaces generic exploration with focused planning methodology
- **Project awareness**: Adapts to each project's conventions and architecture
- **Resumability**: Can be resumed across sessions for iterative refinement
- **Context preservation**: Maintains full analysis context, reducing repetition

The scratchpad-planner agent transforms GitHub issues into concrete, well-structured implementation plans with atomic, reviewable tasks.

## Structure

```
escapement/
├── .claude-plugin/
│   └── plugin.json           # Plugin manifest
├── skills/
│   ├── setup-work/           # GitHub issue -> scratchpad workflow
│   ├── commit-changes/       # Conventional commits
│   ├── create-pr/            # Pull request creation
│   ├── review-pr/            # PR review
│   ├── do-work/              # Execute from scratchpad
│   ├── archive-work/         # Archive completed work (context-path aware)
│   ├── create-issue/         # Ad hoc GitHub issue creation
│   ├── stash-artifact/       # Save artifacts to context directory
│   └── prime-session/        # Project orientation
├── hooks/
│   ├── hooks.json            # Hook configuration
│   └── archive-session-log.sh # PreCompact hook (JSONL copy)
├── scripts/
│   ├── convert-session-log.py # JSONL→markdown session log converter
│   └── migrate-archives.py    # Migrate in-repo archives to context-path
├── agents/                   # Specialized subagents
│   └── scratchpad-planner.md # Codebase analysis for setup-work
├── docs/                     # Extended documentation
│   ├── WORKFLOW.md           # Workflow explanation
│   ├── CUSTOMIZATION.md      # How to customize
│   └── CONTEXT_PATH.md       # Context path design and usage
├── workflow.png              # Workflow diagram
└── README.md                 # This file
```

## Philosophy

**Escapement workflow principles:**

1. **Structured approach** - Clear workflow from issue to merge
2. **Incremental progress** - Atomic commits, reviewable changes
3. **Project awareness** - Adapts to each project's conventions
4. **Multi-project friendly** - Works across all your repos

## Per-Project Customization

Escapement works across multiple projects. Each project customizes its workflow via its own `CLAUDE.md` file:

```markdown

# In your-project/CLAUDE.md

## Project Modules

- **api**: REST API endpoints
- **frontend**: React UI components
- **database**: Database layer

## Commit Message Format

{module emoji}{change type emoji} {type}({scope}): {description}

Example: feat(api): Add user authentication endpoint

```

See `docs/CUSTOMIZATION.md` for detailed examples and patterns.

## Context Path

By default, development artifacts (session logs, archives) live inside your code repo. For larger projects this causes search pollution, repo bloat, and noisy diffs.

The **context-path** feature redirects these artifacts to a sibling directory outside the code repo. Projects opt in by adding to their `CLAUDE.md`:

```markdown
## Escapement Settings

- **context-path**: ../myproject-ctx
```

When set:
- **`archive-work`** archives scratchpads and session logs to `{context-path}/{branch}/archive/` instead of `docs/dev/cc-archive/`
- **`archive-work`** also maintains `{context-path}/INDEX.md` — a chronological table of all archived work across branches (oldest-first)
- **`stash-artifact`** saves ad hoc scripts and notes to `{context-path}/{branch}/scripts/` or `{context-path}/{branch}/notes/`

Note: The PreCompact hook always writes `SESSION_LOG_{N}.jsonl` to the project root (alongside the scratchpad). Session logs are converted to markdown and moved to the context directory by `archive-work` at archive time.

When not set, all behavior is unchanged.

The context directory is plain markdown files that can be optionally git-tracked and work well with tools like Obsidian. See `docs/CONTEXT_PATH.md` for the full design.

## Development

### Adding a New Skill

1. Create directory: `skills/your-skill-name/`
2. Create `SKILL.md` with frontmatter:
   ```markdown
   ---
   name: your-skill-name
   description: What this skill does. Invoke when user says "trigger phrase".
   tools:
     - mcp__github__*
     - Read
     - Write
   ---

   # Your Skill

   ## Purpose
   ...
   ```
3. Test: `claude --plugin-dir /path/to/escapement`
4. Commit and push

### Adding a New Agent

1. Create `agents/your-agent.md`
2. Define specialized expertise
3. List required tools in frontmatter
4. Test: `claude --plugin-dir /path/to/escapement`
5. Commit and push

### Adding Hooks

Edit `hooks/hooks.json` following the [Claude Code hooks documentation](https://code.claude.com/docs/en/hooks).

## Multi-Project Support

Escapement is installed **once** as a plugin but works across **all your projects**:

```bash
# Load plugin
claude --plugin-dir /path/to/escapement

# Per-project customization
~/projects/project-a/CLAUDE.md    # Project A's conventions
~/projects/project-b/CLAUDE.md    # Project B's conventions
~/projects/relica/CLAUDE.md       # Relica's conventions
```

Skills automatically detect the current project and read its `CLAUDE.md` for project-specific settings.

## Troubleshooting

### Plugin not loading

```bash
# Verify plugin structure
ls -la /path/to/escapement/.claude-plugin/

# Should show:
# plugin.json

# Check manifest is valid JSON
cat /path/to/escapement/.claude-plugin/plugin.json | jq .
```

### Skills not appearing

```bash
# Verify skills exist
ls -la /path/to/escapement/skills/

# Restart Claude Code with plugin
claude --plugin-dir /path/to/escapement
```

### Hooks not working

```bash
# Ensure jq is installed
which jq

# Check hooks.json is valid
cat /path/to/escapement/hooks/hooks.json | jq .

# Verify hook script is executable
ls -la /path/to/escapement/hooks/archive-session-log.sh
```

## Contributing

Contributions welcome! To contribute:

1. Fork or clone this repo
2. Create feature branch
3. Add/modify skills, hooks, or agents
4. Test with `claude --plugin-dir ./escapement`
5. Submit PR with description of changes

## License

MIT

## Maintainer

fusupo

## Version

**Current:** 3.6.0

**Changelog:**
- 3.6.0 (2026-02-26): Archive migration and chronological ordering (#31)
  - **Migration script** (#31): `scripts/migrate-archives.py` copies in-repo archives (`docs/dev/cc-archive/`) to context-path structure and backfills INDEX.md
  - **Chronological ordering**: INDEX.md now uses oldest-first ordering (both migration script and `archive-work` skill)
  - **In-repo archives removed**: Historical archives migrated to context-path, `docs/dev/cc-archive/` deleted
- 3.5.0 (2026-02-26): Session archiving pipeline overhaul (#25, #26, #27)
  - **INDEX.md manifest** (#25): `archive-work` maintains a chronological table at the context-path root tracking all archived work across branches
  - **Simplified PreCompact hook** (#27): Hook now copies raw JSONL transcript instead of parsing; `archive-work` converts JSONL→markdown at archive time
  - **Hook write location fix** (#26): Hook always writes `SESSION_LOG_{N}.jsonl` to project root, not context directory
  - **Reusable conversion script**: `scripts/convert-session-log.py` for JSONL→markdown conversion
- 3.4.0 (2026-02-18): Add create-issue skill for ad hoc GitHub issue creation
  - New `create-issue` skill for capturing ideas mid-flow without leaving session
  - Conversational refinement scales to prompt vagueness
  - Optional chaining to `setup-work` for immediate follow-through
- 3.3.0 (2026-02-15): Add context-path support for external artifact storage
  - New `stash-artifact` skill for saving scripts/notes to context directory
  - `archive-work` v2.0.0 with dual-mode archive (context/in-repo)
  - PreCompact hook writes session logs to context directory when configured
  - Portable shell scripts (BSD/macOS compatible)
- 3.2.0 (2026-02-08): Add explicit plan approval gate to setup-work
- 3.1.2 (2026-02-08): Exclude workflow artifacts from commits
- 3.1.1 (2026-01-09): Add directive to omit Claude attribution in git messages
- 3.1.0 (2026-01-09): Integrate Serena MCP for semantic code intelligence
- 3.0.0 (2026-01-02): Renamed project from "muleteer" to "escapement"
  - Breaking change: plugin name changed
  - Updated all references and branding
- 2.0.0 (2025-12-31): Converted to Claude Code plugin architecture
  - Replaced symlink installation with plugin manifest
  - Moved hooks to `hooks/hooks.json` with `${CLAUDE_PLUGIN_ROOT}`
  - Removed install.sh and uninstall.sh
  - Updated skill tool specifications
- 1.0.0 (2025-12-27): Initial Escapement release
  - Generic workflow system
  - Multi-project support
  - Migrated from CRG-specific implementation

Escapement

Claude Code plugin for structured development workflows. Regulated workflow, one tick at a time.

What This Is

Escapement is an opinionated workflow and Claude Code plugin that provides reusable modules to streamline your development process:

meta-workflow: A prescribed sequential process supported by the plugin modules
Skills: Automated workflow modules (issue setup, commits, PRs, etc.)
Hooks: Session archiving on compaction
Agents: Specialized AI assistants (scratchpad-planner for codebase analysis)
Multi-Project Support: Works across all your repos simultaneously

Workflow Overview

Escapement guides you from idea to merged code through a structured workflow:

Initialize (setup-work) - Pull GitHub issue → Generate scratchpad plan → Create feature branch
Execute (do-work + commit-changes) - Work through scratchpad tasks → Make atomic commits
Review (create-pr + review-pr) - Create pull request → Review changes → Merge
Archive (archive-work) - Clean up scratchpad → Preserve session history

High-level workflow diagram

Each phase is handled by specialized skills that activate via natural language or explicit commands.

Installation

From Source (Development)

# Clone the repository
git clone https://github.com/fusupo/escapement.git

# Run Claude Code with the plugin
claude --plugin-dir /path/to/escapement

From Marketplace (Coming Soon)

# Once published to a marketplace
/plugin install escapement

Usage

High-Level Workflow

Work proceeds through four phases:

Initialize: establish scope and plan
Execute: implement planned work in small steps
Review: validate and merge changes
Archive: preserve artifacts and session history

The phases are sequential but not strictly linear; refinement can push work backward before execution begins.

Initialize (`prime-session`, `setup-work`)

The session begins either from an idea or an existing GitHub issue.

If needed, project context is loaded by reading CLAUDE.md and related documentation. An issue is created or fetched, then analyzed to produce a scratchpad plan.

If the issue is too large, it is decomposed into sub-issues. If assumptions are invalid, the issue may be reworked before proceeding.

A feature branch is created once the plan is acceptable.

Operator involvement is primarily directional: clarifying intent and approving scope.

Initialize phase subdiagram

Execute (`do-work`, `commit-changes`)

Work is driven by the scratchpad.

Tasks are selected one at a time, implemented, and committed as atomic changes following project conventions. This loop continues until the scratchpad is complete.

The operator may intervene to adjust task order, clarify intent, or pause execution, but most actions are automated.

Execute phase subdiagram

Review (`create-pr`, `review-pr`)

A pull request is created with full context from the scratchpad and commit history.

The PR is reviewed. If changes are requested, work resumes and new commits are added before re-review.

This cycle repeats until the changes are accepted and merged.

Operator involvement is typically focused on decision-making and judgment rather than mechanics.

Review phase subdiagram

Archive (`archive-work`, hooks)

After merge, the scratchpad is archived.

Before Claude Code compacts the session, the transcript is saved via the PreCompact hook. This preserves planning, execution, and review context as durable artifacts.

The session is then considered complete.

Archive phase subdiagram

Full Workflow Map

This diagram shows all phases together, with swimlanes for each skill and the operator.

It illustrates where decisions occur, which actions are automated, and how control moves between skills over the life of a session.

Full swimlaned workflow diagram

Skills

Skills are invoked automatically by Claude Code when relevant, or you can reference them explicitly with the /escapement: prefix:

Natural Language Invocation:

# Claude uses the skill automatically based on context
"Setup GitHub issue #42"
"Commit these changes"
"Create a PR for this branch"

Explicit Invocation:

/escapement:setup-work
/escapement:commit-changes
/escapement:create-pr

Available Skills

Skill	Triggers	Purpose
`setup-work`	"setup issue #X", "start issue #X"	Fetch issue, create scratchpad, prepare branch
`commit-changes`	"commit", "commit these changes"	Smart commits with conventional format
`create-pr`	"create a PR", "open pull request"	Context-aware PR creation
`review-pr`	"review PR #X", "check this PR"	Roadmap-aware code review
`do-work`	"start working", "continue work"	Execute tasks from scratchpad
`archive-work`	"archive this work", "clean up"	Move completed scratchpads to archive
`create-issue`	"create an issue", "file a bug"	Ad hoc GitHub issue creation from natural language
`stash-artifact`	"stash this script", "save to context"	Save artifacts to context directory
`prime-session`	"orient me", "what is this project"	Read project docs for context

Hooks

Escapement includes a PreCompact hook that captures your raw session transcript before Claude Code's automatic compaction. The hook copies the JSONL transcript to SESSION_LOG_{N}.jsonl in the project root — a minimal, reliable preservation step.

The archive-work skill later converts these .jsonl files to readable markdown (using scripts/convert-session-log.py) and moves them to the archive directory.

Requirements: jq must be installed for the hook to function.

Agents

Specialized subagents for delegation and deep analysis:

scratchpad-planner

Automatically invoked during setup-work (Phase 2) for codebase analysis and implementation planning.

Capabilities:

Reads project's CLAUDE.md for conventions and structure
Analyzes codebase using Grep, LSP, and code search patterns
Identifies affected modules and integration points
Finds similar implementations to learn from
Generates atomic task breakdowns following project conventions
Asks clarifying questions for ambiguous requirements
Supports resumable analysis for complex codebases

Benefits:

Specialized expertise: Replaces generic exploration with focused planning methodology
Project awareness: Adapts to each project's conventions and architecture
Resumability: Can be resumed across sessions for iterative refinement
Context preservation: Maintains full analysis context, reducing repetition

The scratchpad-planner agent transforms GitHub issues into concrete, well-structured implementation plans with atomic, reviewable tasks.

Structure

escapement/
├── .claude-plugin/
│   └── plugin.json           # Plugin manifest
├── skills/
│   ├── setup-work/           # GitHub issue -> scratchpad workflow
│   ├── commit-changes/       # Conventional commits
│   ├── create-pr/            # Pull request creation
│   ├── review-pr/            # PR review
│   ├── do-work/              # Execute from scratchpad
│   ├── archive-work/         # Archive completed work (context-path aware)
│   ├── create-issue/         # Ad hoc GitHub issue creation
│   ├── stash-artifact/       # Save artifacts to context directory
│   └── prime-session/        # Project orientation
├── hooks/
│   ├── hooks.json            # Hook configuration
│   └── archive-session-log.sh # PreCompact hook (JSONL copy)
├── scripts/
│   ├── convert-session-log.py # JSONL→markdown session log converter
│   └── migrate-archives.py    # Migrate in-repo archives to context-path
├── agents/                   # Specialized subagents
│   └── scratchpad-planner.md # Codebase analysis for setup-work
├── docs/                     # Extended documentation
│   ├── WORKFLOW.md           # Workflow explanation
│   ├── CUSTOMIZATION.md      # How to customize
│   └── CONTEXT_PATH.md       # Context path design and usage
├── workflow.png              # Workflow diagram
└── README.md                 # This file

Philosophy

Escapement workflow principles:

Structured approach - Clear workflow from issue to merge
Incremental progress - Atomic commits, reviewable changes
Project awareness - Adapts to each project's conventions
Multi-project friendly - Works across all your repos

Per-Project Customization

Escapement works across multiple projects. Each project customizes its workflow via its own CLAUDE.md file:


# In your-project/CLAUDE.md

## Project Modules

- **api**: REST API endpoints
- **frontend**: React UI components
- **database**: Database layer

## Commit Message Format

{module emoji}{change type emoji} {type}({scope}): {description}

Example: feat(api): Add user authentication endpoint

See docs/CUSTOMIZATION.md for detailed examples and patterns.

Context Path

By default, development artifacts (session logs, archives) live inside your code repo. For larger projects this causes search pollution, repo bloat, and noisy diffs.

The context-path feature redirects these artifacts to a sibling directory outside the code repo. Projects opt in by adding to their CLAUDE.md:

## Escapement Settings

- **context-path**: ../myproject-ctx

When set:

archive-work archives scratchpads and session logs to {context-path}/{branch}/archive/ instead of docs/dev/cc-archive/
archive-work also maintains {context-path}/INDEX.md — a chronological table of all archived work across branches (oldest-first)
stash-artifact saves ad hoc scripts and notes to {context-path}/{branch}/scripts/ or {context-path}/{branch}/notes/

Note: The PreCompact hook always writes SESSION_LOG_{N}.jsonl to the project root (alongside the scratchpad). Session logs are converted to markdown and moved to the context directory by archive-work at archive time.

When not set, all behavior is unchanged.

The context directory is plain markdown files that can be optionally git-tracked and work well with tools like Obsidian. See docs/CONTEXT_PATH.md for the full design.

Development

Adding a New Skill

Create directory: skills/your-skill-name/

Create SKILL.md with frontmatter:

---
name: your-skill-name
description: What this skill does. Invoke when user says "trigger phrase".
tools:
  - mcp__github__*
  - Read
  - Write
---

# Your Skill

## Purpose
...

Test: claude --plugin-dir /path/to/escapement
Commit and push

Adding a New Agent

Create agents/your-agent.md
Define specialized expertise
List required tools in frontmatter
Test: claude --plugin-dir /path/to/escapement
Commit and push

Adding Hooks

Edit hooks/hooks.json following the Claude Code hooks documentation.

Multi-Project Support

Escapement is installed once as a plugin but works across all your projects:

# Load plugin
claude --plugin-dir /path/to/escapement

# Per-project customization
~/projects/project-a/CLAUDE.md    # Project A's conventions
~/projects/project-b/CLAUDE.md    # Project B's conventions
~/projects/relica/CLAUDE.md       # Relica's conventions

Skills automatically detect the current project and read its CLAUDE.md for project-specific settings.

Troubleshooting

Plugin not loading

# Verify plugin structure
ls -la /path/to/escapement/.claude-plugin/

# Should show:
# plugin.json

# Check manifest is valid JSON
cat /path/to/escapement/.claude-plugin/plugin.json | jq .

Skills not appearing

# Verify skills exist
ls -la /path/to/escapement/skills/

# Restart Claude Code with plugin
claude --plugin-dir /path/to/escapement

Hooks not working

# Ensure jq is installed
which jq

# Check hooks.json is valid
cat /path/to/escapement/hooks/hooks.json | jq .

# Verify hook script is executable
ls -la /path/to/escapement/hooks/archive-session-log.sh

Contributing

Contributions welcome! To contribute:

Fork or clone this repo
Create feature branch
Add/modify skills, hooks, or agents
Test with claude --plugin-dir ./escapement
Submit PR with description of changes

License

MIT

Maintainer

fusupo

Version

Current: 3.6.0

Changelog:

3.6.0 (2026-02-26): Archive migration and chronological ordering (#31)
- Migration script (#31): scripts/migrate-archives.py copies in-repo archives (docs/dev/cc-archive/) to context-path structure and backfills INDEX.md
- Chronological ordering: INDEX.md now uses oldest-first ordering (both migration script and archive-work skill)
- In-repo archives removed: Historical archives migrated to context-path, docs/dev/cc-archive/ deleted
3.5.0 (2026-02-26): Session archiving pipeline overhaul (#25, #26, #27)
- INDEX.md manifest (#25): archive-work maintains a chronological table at the context-path root tracking all archived work across branches
- Simplified PreCompact hook (#27): Hook now copies raw JSONL transcript instead of parsing; archive-work converts JSONL→markdown at archive time
- Hook write location fix (#26): Hook always writes SESSION_LOG_{N}.jsonl to project root, not context directory
- Reusable conversion script: scripts/convert-session-log.py for JSONL→markdown conversion
3.4.0 (2026-02-18): Add create-issue skill for ad hoc GitHub issue creation
- New create-issue skill for capturing ideas mid-flow without leaving session
- Conversational refinement scales to prompt vagueness
- Optional chaining to setup-work for immediate follow-through
3.3.0 (2026-02-15): Add context-path support for external artifact storage
- New stash-artifact skill for saving scripts/notes to context directory
- archive-work v2.0.0 with dual-mode archive (context/in-repo)
- PreCompact hook writes session logs to context directory when configured
- Portable shell scripts (BSD/macOS compatible)
3.2.0 (2026-02-08): Add explicit plan approval gate to setup-work
3.1.2 (2026-02-08): Exclude workflow artifacts from commits
3.1.1 (2026-01-09): Add directive to omit Claude attribution in git messages
3.1.0 (2026-01-09): Integrate Serena MCP for semantic code intelligence
3.0.0 (2026-01-02): Renamed project from "muleteer" to "escapement"
- Breaking change: plugin name changed
- Updated all references and branding
2.0.0 (2025-12-31): Converted to Claude Code plugin architecture
- Replaced symlink installation with plugin manifest
- Moved hooks to hooks/hooks.json with ${CLAUDE_PLUGIN_ROOT}
- Removed install.sh and uninstall.sh
- Updated skill tool specifications
1.0.0 (2025-12-27): Initial Escapement release
- Generic workflow system
- Multi-project support
- Migrated from CRG-specific implementation