Enjinia — Productivity skill for Claude Code

An engineering lifecycle for agent teams.

Enjinia is a Claude Code plugin that runs a software engineering workflow like a senior engineer. A team of agents takes a ticket through requirements, conceptual design, application design, implementation and review. Each stage ends at a gate: a check that must pass, and a human approval where your autonomy level asks for one. Each stage leaves its evidence in files. You own the decisions that matter and can delegate the rest.

Example

In Claude Code, inside the repo you want to change:

/enjinia:lifecycle Retry failed webhook deliveries with backoff

Enjinia sizes the work, then asks you questions until the requirements are stable. It writes each stage's output to a feature folder in your repo:

docs/specs/webhook-retry/
  triage.md         size, mode, domain packs, autonomy level
  as-is.md          existing code only: the current design of what the change touches
  requirements.md   requirements with IDs (BR-1, FR-2, NFR-1)
  concept.md        the model and its invariants (INV-1), with a TLA+ check
  design.md         components, flows and slices
  adr/001-*.md      decision records; a decision an agent made is tagged auto
  tasks.yaml        the task plan: tasks with depends_on, run in dependency order
  review.md         gate results with evidence

Every test names the requirements it covers. At each gate, a script (`core/scripts/trace_check.py`) checks that each requirement traces to an invariant, a component, a task and a passing test.

The lifecycle

Stage	Output	What happens
0 Triage	triage.md	Size, new or existing codebase, domain packs, autonomy level
1 Requirements	requirements.md	An interview, at most 4 questions per round, wi