execution-set-up

A framework for setting up autonomous, agent-driven work in a project. You get one lightweight skill; it bootstraps the rest.

What it ships

• to-execution, the skill (src/SKILL.md). The Team Lead invokes it in a new project. It runs Preflight → stamps the layout → grills the user → hands off.
• to-execution, the npm package (src/). The skill runs npx to-execution init to deterministically stamp the invariant layout. The agent writes only the variant (grilled) files.

The split is the point: identical-across-projects files are stamped by the package (no read→write drift); project-specific files are written by the agent during the grill.

What a set-up project gets

.excn/                       everything the framework owns (ADR-0002)
├── CONTEXT.md               glossary + team roster                  (grilled)
├── PHILOSOPHY.md            project working philosophies            (grilled)
├── PROCESS.md               the Lifecycle + Retro Loop              (invariant)
├── TEAM_DIRECTIVE.md        roster, routing, QA gates               (grilled)
├── adr/                     design-time decision records
├── research/                durable research reports
├── schemas/                 sprint / issue / prd / progress JSON    (invariant)
└── sprints/ issues/ prds/ retros/   flat work-tracking (ephemeral, self-gitignored)
.claude/agents/              scribe + process-adherence + alignment (stamped) + grilled team
CLAUDE.md / AGENTS.md        host's own files — wired with an append-only pointer block, never overwritten

How work runs once set up

grill → PRD → issues → sprint → retro → edits of persistent docs & Teammate definitions

Setup and work are separate sessions: the Setup Grill stops at handoff; the grill family (execution-context-grill → execution-epic-grill → execution-to-prd → execution-to-issues) starts sprint 1 in a fresh session.

This repo is its own first customer

src/ is the product. The repo root is a dogfood Instance — stamped once from src/template/ and maintained Src-First: framework changes land in src/, then the root is updated to match. See CONTEXT.md for the full glossary of terms (Template, Instance, Src-First, Teammate, Invoked Agent, Adherence Agent, Lifecycle, Retro Loop, Principles, Philosophy).

Develop

node src/bin/cli.js --help              # CLI surface
node src/bin/cli.js init <target>       # stamp the invariant layout into a project