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
Extract workflow, branching, PRs, and session rules from
AGENTS.md into docs/WORKFLOW.md. Move features.json and
claude-progress.txt format specs into dedicated reference
files. Slim AGENTS.md down to project overview and
knowledge base table.
Add init.sh to start and stop the dev environment with
port readiness checks. Update init-session command to
cover startup steps 1-6.
Co-Authored-By: Claude <noreply@anthropic.com>
3. Read `docs/agent-struggles.json` — if unresolved entries exist, present to user
33
-
4. Read `docs/features.json` — pick first `"passes": false` entry
34
-
5. Run `./init.sh` — start dev env
35
-
6. Run tests — verify app is healthy
36
-
7. If broken → fix first. If clean → start [Feature Development Sequence](#feature-development-sequence).
37
-
38
-
## Branching
39
-
40
-
Create a feature branch per plan: `<NNN>-<type>-<short-name>` where `<NNN>` matches the plan number and `<type>` the
41
-
conventional commit type as per our [Git Commit Guide](/docs/references/commit-message-agent-readme.md#conventional-commits). Example: `001-feat-function-list-empty-state`.
42
-
43
-
## Feature Development Sequence
44
-
45
-
After [Startup Sequence](#startup-sequence), work through the picked feature:
46
-
47
-
1.**Plan** — read `docs/ARCHITECTURE.md` + `docs/STYLEGUIDE.md` + `docs/TESTING.md`, then create implementation plan → `docs/plans/active/<incremented-number>-feature-<short-name>.md`
48
-
2.**Branch** — create feature branch per [Branching](#branching) convention
49
-
3.**Implement** — using `/executing-plans` skill
50
-
4.**Review** — code review using `/requesting-code-review` skill, fix found issues
51
-
5.**Manual Test** — use browser automation and validate it works in the browser
52
-
6.**Complete** — flip `passes` to `true` in `docs/features.json`, update `docs/claude-progress.txt`, commit
53
-
7.**PR** — push branch, open PR via `gh pr create` using `.github/pull_request_template.md`
54
-
8. Move plan to `docs/plans/completed/`
55
-
9. Stop, wait for user command
56
-
57
-
## Session Rules
58
-
59
-
- One feature at a time
60
-
- Clean state at end (code suitable for merging to main)
61
-
- Update `docs/claude-progress.txt` before session ends
62
-
- Commit work to git before ending — follow `docs/references/commit-message-agent-readme.md` strictly
63
-
64
-
## features.json
65
-
66
-
Inviolable. The categories are `functional` or `technical`. You may only change the `passes` field to `true` — and only after:
67
-
68
-
1. The corresponding e2e test passes
69
-
2. You have validated the feature in a real browser via browser automation
70
-
71
-
Never remove, reorder, or edit feature entries. Work on the first entry where `passes` is `false`.
72
-
73
-
Format:
74
-
75
-
```json
76
-
{
77
-
"category": "functional",
78
-
"description": "...",
79
-
"steps": ["..."],
80
-
"passes": false
81
-
}
82
-
```
83
-
84
-
## claude-progress.txt
85
-
86
-
Append-only, newest-first. Add your entry at the top after the header. Format:
87
-
88
-
```txt
89
-
---
90
-
## YYYY-MM-DD | Session: <brief title>
91
-
Worked on: <what you did>
92
-
Completed:
93
-
- <item>
94
-
Left off: <what remains>
95
-
Blockers: <any blockers or None>
96
-
```
97
-
98
-
## Continuous Improvement
99
-
100
-
When you struggle, don't silently work around it. Log it to `docs/agent-struggles.json`:
3. Read `docs/agent-struggles.json` — if unresolved entries exist, present to user
10
+
4. Read `docs/features.json` — pick first `"passes": false` entry
11
+
5. Run `./init.sh` — start dev env
12
+
6. Run tests — verify app is healthy
13
+
7. If broken → fix first. If clean → start [Feature Development Sequence](#feature-development-sequence).
14
+
15
+
## Feature Development Sequence
16
+
17
+
After [Startup Sequence](#startup-sequence), work through the picked feature:
18
+
19
+
1.**Plan** — read `docs/ARCHITECTURE.md` + `docs/STYLEGUIDE.md` + `docs/TESTING.md`, then create implementation plan → `docs/plans/active/<incremented-number>-feature-<short-name>.md`
20
+
2.**Branch** — create feature branch per [Branching](#branching) convention
21
+
3.**Implement** — using `/executing-plans` skill
22
+
4.**Review** — code review using `/requesting-code-review` skill, fix found issues
23
+
5.**Manual Test** — use browser automation and validate it works in the browser
24
+
6.**Complete** — flip `passes` to `true` in [`docs/features.json`](references/features-json-readme.md), update [`docs/claude-progress.txt`](references/claude-progress-readme.md), commit
25
+
7.**PR** — push branch, open PR per [Pull Requests](#pull-requests) convention
26
+
8. Move plan to `docs/plans/completed/`
27
+
9. Stop, wait for user command
28
+
29
+
## Branching
30
+
31
+
Create a feature branch per plan: `<NNN>-<type>-<short-name>` where `<NNN>` matches the plan number and `<type>` the conventional commit type as per our [Git Commit Guide](references/commit-message-agent-readme.md#conventional-commits). Example: `001-feat-function-list-empty-state`.
32
+
33
+
## Pull Requests
34
+
35
+
Open PRs via `gh pr create` using the template at `.github/pull_request_template.md`.
36
+
37
+
**Title format:**`<Type>: <Sentence ending with a period.>` — capitalize the type and the first word, end with a period. Example: `Feat: Add function list page with empty state.`
38
+
39
+
Types are the same as [conventional commits](references/commit-message-agent-readme.md#conventional-commits) but capitalized.
40
+
41
+
## Session Rules
42
+
43
+
- One feature at a time
44
+
- Clean state at end (code suitable for merging to main)
45
+
- Update [`docs/claude-progress.txt`](references/claude-progress-readme.md) before session ends
46
+
- Commit work to git before ending — follow [`docs/references/commit-message-agent-readme.md`](references/commit-message-agent-readme.md) strictly
47
+
48
+
## Continuous Improvement
49
+
50
+
When you struggle, don't silently work around it. Log it to `docs/agent-struggles.json` — see [`docs/references/agent-struggles-readme.md`](references/agent-struggles-readme.md) for format.
0 commit comments