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
Layer 1.5: generate .claude/agents/ alongside skills during parallax init.
4 scientific agents (hypothesis-explorer, experiment-runner, literature-reviewer,
result-validator) with model selection by token tier (pro/5x/20x/api).
Auto-refinement via claude CLI, parallax config set token-tier, session-start
skill, memory:project on hypothesis+experiment. Plan archival + verification
rules in CLAUDE.md.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
.claude/hooks/ # Hook enforcement scripts for Parallax development
@@ -105,8 +107,13 @@ pixi run check # all of the above
105
107
- Never add backward-compat shims — just change the code
106
108
- Never create docs/READMEs unless explicitly requested
107
109
108
-
## Documentation Maintenance
110
+
## Plan Completion & Verification
109
111
112
+
-**Archive the plan.** At the start of implementation, copy the plan file to `docs/plans/NNN_short-name.md` (next sequence number). The plan path is in the system message from plan mode.
113
+
- Every plan's verification section is **mandatory**. At the end of implementation:
114
+
1.**List all verification commands** from the plan so the user can run them independently
115
+
2.**Execute each one** and report the result (pass/fail, key output) explicitly to the user
116
+
-`pixi run check` is baseline; also run any CLI smoke tests or manual checks the plan specifies
110
117
- At the end of every plan, verify README.md and other markdown docs reflect current state
111
118
- If code changes affect documented behavior, update the relevant docs in the same PR
112
119
-@README.md and other key docs should be reviewed before marking any plan complete
0 commit comments