You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This file provides guidance to Claude Code when working with this repository.
4
4
5
5
This project is a Claude Code plugin marketplace containing **skills** — structured markdown workflow documents. There is no application code or build system. Skills are validated by a three-layer test pipeline (see Testing Skills below).
6
6
7
-
For project architecture, key concepts (RPI methodology, testing philosophy, hexagonal architecture), artifact lifecycle, and installation commands, see `docs/architecture.md`.
7
+
The core workflow follows the **RPI methodology** (Research → Plan → Implement) for non-trivial features. Skills are validated by a three-layer test pipeline (see Testing Skills below).
Each phase flows directly into the next. Context clearing is only suggested when the conversation is extensive — the artifacts carry all needed context forward.
46
+
45
47
## Creating New Skills
46
48
47
49
Use the Anthropic `/skill-creator` skill to guide you through creating new skills. It provides an interactive workflow for designing effective skill documents.
@@ -51,8 +53,7 @@ Before creating a skill, review the Skill Authoring Guidelines and Frontmatter F
|**adr**|`/adr`| Guides writing minimal Architecture Decision Records |
47
44
|**reflect**|`/reflect`| Post-session reflection that mines git history and artifacts to produce improvement proposals |
48
45
49
-
####RPI Methodology (Research → Plan → Implement)
46
+
### RPI Methodology (Research → Plan → Implement)
50
47
51
-
The light factory praxis plugin's core workflow for non-trivial features:
48
+
The praxis plugin's core workflow for non-trivial features follows three phases:
52
49
53
-
1.**Research** (`/research`) — Explore the codebase with parallel subagents, output a compact research artifact
54
-
2.**Plan** (`/plan-tasks`) — Consume the research artifact, produce a compact implementation plan with test specs
50
+
1.**Research** (`/research`) — Explore the codebase with parallel subagents, output a compact research artifact to `.light/sessions/`
51
+
2.**Plan** (`/plan-tasks`) — Consume the research artifact, produce a compact implementation plan with test specs and Agent Context blocks
55
52
3.**Implement** (`/implement`) — Execute the plan phase by phase with strict RED → GREEN → VALIDATE discipline
56
53
54
+
#### Key Concepts
57
55
58
-
### Harness Plugin: used for harness engineering flow
56
+
-**Plan Mode Native** — The workflow aligns with Claude Code's native plan mode. Research happens outside plan mode; planning activates draft behavior inside plan mode; implementation executes the approved plan.
57
+
-**Three-Agent TDD Isolation** — During implementation, each TDD phase dispatches isolated agents: `agent-test` (writes failing tests), `agent-impl` (writes minimal code to pass), and `agent-validate` (runs full test suite). Agents never modify each other's artifacts.
58
+
-**Context Compaction** — Research produces a ~200-line artifact that carries forward into planning, replacing unbounded codebase exploration with a focused summary. Plan mode entry is the compaction boundary.
59
+
-**Tracker Detection Chain** — The implement and plan-tasks skills auto-detect available task trackers: yaks (preferred) → beads (fallback) → native tasks (last resort).
59
60
61
+
#### Standalone Skills
60
62
61
-
| Skill | Command | Description |
62
-
|-------|---------|-------------|
63
-
|**diagram**|`/diagram`| Creates architecture diagrams (C4 structural, dynamic flows, data flow) with subtype dispatch |
64
-
|**scaffold**|`/scaffold`| Scaffolds DDD projects from Gherkin feature files with language subtype dispatch |
|**adr**|`/adr`| Guides writing minimal Architecture Decision Records |
67
-
|**distill**|`/distill`| Distills an agentic engineering harness from a project with DDD structures and fitness tests |
63
+
-**TDD** (`/tdd`) — For interactive, human-in-the-loop test-driven development outside the full RPI flow. Enforces boundary-focused testing at the L3/L4 altitude with ZOMBIES progression.
64
+
-**ADR** (`/adr`) — Guides writing Architecture Decision Records following the Harmel-Law signal check pattern. Ensures decisions are actually made before documenting them.
65
+
-**Reflect** (`/reflect`) — Post-session learning loop that mines git history and session artifacts to produce improvement proposals for skills, CLAUDE.md, and hooks.
68
66
69
67
## Testing
70
68
@@ -87,5 +85,3 @@ cd tests/evals && promptfoo eval
87
85
## Contributing
88
86
89
87
See `AGENTS.md` for skill authoring guidelines, testing workflows, and the pre-ship checklist.
90
-
91
-
See `docs/architecture.md` for project structure and key concepts.
0 commit comments