skynet/agent-runtime-framework
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(harness): align workspace paths and best-practices mount target

Browse Source 
- Mount best-practices context at /workspace/best-practices/ (was
  /opt/harness/context/best-practices/) for consistent agent access
- Fix /workspace/working/ → /workspace/project/ in all CLAUDE.md files
  (planning, spec-writing, security-review, code-methodology,
  qwen-code-methodology, test-writing)
- Update best-practices path references in all CLAUDE.md files to
  /workspace/best-practices/

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Paul O'Reilly
2026-04-28 13:24:10 +12:00
parent b04f718530
commit c0758cbd71
7 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
harnesses/contexts/spec-writing/v1/CLAUDE.md
View File

@@ -4,7 +4,7 @@ You are a specification writing agent. Your job is to produce detailed, testable
## Required Reading
Before starting any spec, read these from `/opt/harness/context/best-practices/`:
Before starting any spec, read these from `/workspace/best-practices/`:
| File | Priority |
|---|---|
@@ -43,10 +43,10 @@ Every spec must follow this structure:
## Output Conventions
- **If `/workspace/working/` exists** (agent-repo mode): write spec files to `/workspace/working/spec/<name>.md`. Edit existing specs in place.
- **If `/workspace/working/` does not exist**: write to `/workspace/.agent-output/output.md`
- **If `/workspace/project/` exists** (agent-repo mode): write spec files to `/workspace/project/spec/<name>.md`. Edit existing specs in place.
- **If `/workspace/project/` does not exist**: write to `/workspace/.agent-output/output.md`
- **NEVER write to `/workspace/spec/`** — that path is outside the git working tree and the file will not be committed.
- **NEVER write to `/workspace/.agent-output/` when `/workspace/working/` exists** — that directory is gitignored.
- **NEVER write to `/workspace/.agent-output/` when `/workspace/project/` exists** — that directory is gitignored.
- Use the project's existing requirement prefix convention if one exists
- Cross-reference other specs by filename when declaring dependencies
@@ -54,9 +54,9 @@ Every spec must follow this structure:
Before writing your session log and exiting, run these checks:
1. `ls /workspace/working/spec/<your-spec-file>.md` — confirm the file exists at the correct path
2. `cd /workspace/working && git status` — confirm the file appears as untracked or modified (not ignored)
3. If the file does NOT appear in `git status`, you wrote it to the wrong path — move it to `/workspace/working/spec/` before exiting
1. `ls /workspace/project/spec/<your-spec-file>.md` — confirm the file exists at the correct path
2. `cd /workspace/project && git status` — confirm the file appears as untracked or modified (not ignored)
3. If the file does NOT appear in `git status`, you wrote it to the wrong path — move it to `/workspace/project/spec/` before exiting
## What NOT to Do
@@ -67,7 +67,7 @@ Before writing your session log and exiting, run these checks:
## Session Logging
Write a brief session log to `/workspace/working/memory/log/<date>.<time>.md` (agent-repo mode) or `/workspace/.agent-output/session-log.md` (fallback) with:
Write a brief session log to `/workspace/project/memory/log/<date>.<time>.md` (agent-repo mode) or `/workspace/.agent-output/session-log.md` (fallback) with:
- **Summary**: What specs were written/updated, requirement count
- **Key Decisions**: Design choices and rationale
- **Open Questions**: Anything that needs human input