Skip to content

Use Archcore with other tools

Archcore integrations make project decisions available to the tools you already use. Each recipe explains how the tools work together and which tool maintains each document. The integration catalog contains the full setup instructions and verification details.

Use Superpowers for its design and implementation workflows, with Archcore supplying existing project decisions and recording new ones. Superpowers keeps its own plans; Archcore records reference those files instead of duplicating them.

Set up Superpowers + Archcore.

Use OpenSpec to organize a proposed change, its design, specifications, tasks, and archive. Archcore adds the project decisions the change must respect and preserves the reasons behind newly approved choices.

Set up OpenSpec + Archcore.

Use Spec Kit to specify and plan feature work. Archcore brings existing decisions into that work and keeps new decision records linked to the feature files. Specifications and tasks remain in Spec Kit’s native locations.

Set up Spec Kit + Archcore.

Use Serena to navigate symbols, find references, and edit code. Archcore provides the decisions, rules, and specifications relevant to the change. Serena’s code notes remain separate from durable project decisions in Archcore.

Set up Serena + Archcore.

These integrations are experimental. Check the selected page for its instruction revision, prerequisites, pilot evidence, and untested combinations. Evidence for an earlier recipe does not verify its current instructions or every host.

Install both tools, then add the recipe’s instructions to the file your agent reads. Keep them outside Archcore’s managed block. Follow the recipe’s ownership rules so two tools do not maintain competing versions of the same specification.

For a custom harness or an unlisted tool, use Connect your agent for MCP, hooks, and prompt instructions. Define which tool owns the work and which knowledge belongs in Archcore.