# Archcore + Superpowers

> Connect Archcore + Superpowers to bring project decisions into your agent’s work. Copy the integration instructions and set up your agent.

Instruction revision: 6a803fd329569ae313d1d8cf5330c03fb1971918cf61565f045a5aabbf1d8466
Instruction text: https://archcore.ai/integrations/superpowers/cooperation.md
Source: https://github.com/archcore-ai/plugin — AGENTS.md (unpublished)

## Tools

- Archcore — Keeps project decisions, rules, and specs in Git for your agent to use.
- Superpowers — Guides design and implementation through its own skills and plans.

## How Archcore + Superpowers work together

Start with either tool. These instructions tell your agent to read existing
project decisions before design work and save new decisions in Archcore.
Superpowers keeps its own plans; Archcore documents reference them.

## From a new idea to the next session

The instructions ask your agent to:

1. **Read existing decisions.** At the start of brainstorming, the agent searches Archcore for decisions and rules that apply to your task.
2. **Review the design before code.** Superpowers guides the design. If the task conflicts with an accepted decision, the agent asks you how to proceed.
3. **Keep the decisions you approve.** After design approval, the agent records decisions as draft architecture decision records (ADRs) in Archcore. Accepting an ADR needs your explicit approval.
4. **Continue with project context.** The next session can find the saved design and decisions. Superpowers keeps its implementation plans in the repository.

Starting with /archcore:plan? That command finishes first. Superpowers can pick up design or execution work it leaves open.


## Benefits & limits

### Catch conflicts before code.

The instructions bring existing project decisions into design work. You resolve conflicts before implementation and approve new decisions before they become accepted records.

### Design with project context

Brainstorming starts with a search for relevant decisions and rules.

You approve the design before code is written.

### Conflicting or shared decisions

A conflict with an accepted decision needs your input. Read-only documents stay with their owning project.

If several projects are writable, the agent confirms where to save a record.

### A new session

Saved designs and decisions give the next session context to continue.

Unanswered design questions still need your input.

### Two implementation plans

Superpowers keeps its detailed execution plan. The Archcore plan stays as written.

You maintain any overlapping tasks across the two plans.

### Starting with /archcore:plan

The command finishes before brainstorming begins.

Superpowers can take on design or execution work the command leaves open.

### Limits

These instructions rely on the agent following them. The design-to-ADR step has not been verified end to end.


## Known limits

- Instructions are copied from the Archcore + Superpowers section of AGENTS.md. CLAUDE.md imports that file.
- This instruction revision has no linked verification record.
- The recipe source is unpublished, so the text is pinned by digest rather than by an upstream revision.
- Setup steps are written for five agents and checked on none of them.
- Superpowers is not installed by this recipe. It has to be present and callable already.
- This pair only. Two working pairs do not make a working triple.