feat: add file paths to codebase mapping output
- Agent prompts now explicitly require file paths in findings - Templates updated with backtick-formatted path examples - CONCERNS.md examples show Files: field for every issue - ARCHITECTURE.md now welcomes file paths as concrete examples - Makes codebase docs actionable for Claude during planning 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -103,7 +103,7 @@ Template for `.planning/codebase/STACK.md` - captures the technology foundation.
|
||||
|
||||
**Package Manager:**
|
||||
- npm 10.x
|
||||
- Lockfile: package-lock.json present
|
||||
- Lockfile: `package-lock.json` present
|
||||
|
||||
## Frameworks
|
||||
|
||||
@@ -135,8 +135,8 @@ Template for `.planning/codebase/STACK.md` - captures the technology foundation.
|
||||
- Configuration via CLI flags only
|
||||
|
||||
**Build:**
|
||||
- tsconfig.json - TypeScript compiler options
|
||||
- vitest.config.ts - Test runner configuration
|
||||
- `tsconfig.json` - TypeScript compiler options
|
||||
- `vitest.config.ts` - Test runner configuration
|
||||
|
||||
## Platform Requirements
|
||||
|
||||
|
||||
Reference in New Issue
Block a user