Software Development Skills

Boot a live Archie instance from the current branch, drive E2E scenarios headlessly through the archie-debug MCP (nonce → createtask → waitfortask → approve), capture per-scenario evidence files, and tear down cleanly. Use for Forge Stage 4 QA, verifying a branch against a live instance, running the basic or edit-mode E2E scenario, or when asked to "run the e2e harness", "boot archie for testing", or "verify this AC live".

How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel. Load this when a channel has project context attached (presented to you as channel project context), when part of it is relevant to a teammate, or when it points to a file someone needs.

Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.

Summarize or draft workflow. Use when someone asks to summarize a piece of text, condense a document, draft a short reply, or "TL;DR this". This is the example skill that ships with Archie.

Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can you do", "how do you work", "what are you", "who are you", "are you able to...", "do you have access to...", "can you change yourself", "can you add a plugin", "what's your architecture", "how do you handle...", "what happens when...". Provides the ground truth needed to answer accurately without inventing capabilities.

Output format for summaries. Load before producing any summary so the result is consistent and skimmable.

Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents vs skills vs PM skills. Triggers on "write a plugin", "add an agent", "add a skill", "create a new domain", "make a new teammate". This is the "how to think about it" layer; the README's Plugins section and docs/architecture/plugin-system.md are the "how to wire it up" layer.