Bug
The archon-interactive-prd workflow's generate node tries to write the PRD file to .claude/PRPs/prds/, but Claude Code blocks writes to the .claude/ directory — even with bypassPermissions. This is a hardcoded safety boundary in the Claude Code SDK.
Steps to Reproduce
- Run
archon workflow run archon-interactive-prd "Build something"
- Complete all approval gates (foundation, deepdive, scope)
- Node
generate attempts: mkdir -p .claude/PRPs/prds && write PRD
- Write is blocked by Claude Code SDK → node fails or produces no output
Confirmed
Run 4c4ec384a38e1e7092f504dcda4c07fd: generate node completed with only 138 chars output (error) instead of the full PRD. Validate node then couldn't find the file.
Suggested Fix
Change the output path in the generate node prompt from:
.claude/PRPs/prds/{kebab-case-name}.prd.md
to:
$ARTIFACTS_DIR/prds/{kebab-case-name}.prd.md
$ARTIFACTS_DIR is pre-created by the executor and always writable. The validate node's prompt should be updated to match.
Related
Bug
The
archon-interactive-prdworkflow'sgeneratenode tries to write the PRD file to.claude/PRPs/prds/, but Claude Code blocks writes to the.claude/directory — even withbypassPermissions. This is a hardcoded safety boundary in the Claude Code SDK.Steps to Reproduce
archon workflow run archon-interactive-prd "Build something"generateattempts:mkdir -p .claude/PRPs/prds && write PRDConfirmed
Run
4c4ec384a38e1e7092f504dcda4c07fd:generatenode completed with only 138 chars output (error) instead of the full PRD. Validate node then couldn't find the file.Suggested Fix
Change the output path in the
generatenode prompt from:to:
$ARTIFACTS_DIRis pre-created by the executor and always writable. Thevalidatenode's prompt should be updated to match.Related
capture_response: true(same workflow)