|
1 | | -# DevMap — Agent |
2 | | - |
3 | | -read PRD and all documentation first before hands-on. |
4 | | - |
5 | | -## Relevant Skills |
6 | | - |
7 | | -ECC skills are stored in `.agents/skills/`. |
8 | | - |
9 | | -Use these when relevant: |
10 | | - |
11 | | -- `coding-standards` — code quality and consistency. |
12 | | -- `verification-loop` — build, lint, typecheck, test, manual verification. |
13 | | -- `documentation-lookup` — check current library docs instead of guessing. |
14 | | -- `backend-patterns` — service/repository/validation patterns. |
15 | | -- `deep-research` — research parser/framework/library behavior. |
16 | | -- `security-review` — secrets, command execution, file access, user input. |
17 | | -- `tdd-workflow` — tests for new analyzers and bug fixes. |
18 | | -- `eval-harness` — benchmark DevMap output on sample repositories. |
19 | | -- `strategic-compact` — keep long agent sessions manageable. |
20 | | -- `agent-introspection-debugging` — recover when the agent loops or gets stuck. |
21 | | - |
| 1 | +# DevMap — Agent |
| 2 | + |
| 3 | +read PRD and all documentation first before hands-on. |
| 4 | + |
| 5 | +## Source of Truth |
| 6 | + |
| 7 | +The PRD is the source of truth for product behavior, requirements, and priorities. |
| 8 | + |
| 9 | +If there is any conflict between the PRD and other documents (README, docs, comments, plans, or specifications), follow the PRD. |
| 10 | + |
| 11 | +## Relevant Skills |
| 12 | + |
| 13 | +ECC skills are stored in `.agents/skills/`. |
| 14 | + |
| 15 | +Use these when relevant: |
| 16 | + |
| 17 | +- `coding-standards` — code quality and consistency. |
| 18 | +- `verification-loop` — build, lint, typecheck, test, manual verification. |
| 19 | +- `documentation-lookup` — check current library docs instead of guessing. |
| 20 | +- `backend-patterns` — service/repository/validation patterns. |
| 21 | +- `deep-research` — research parser/framework/library behavior. |
| 22 | +- `security-review` — secrets, command execution, file access, user input. |
| 23 | +- `tdd-workflow` — tests for new analyzers and bug fixes. |
| 24 | +- `eval-harness` — benchmark DevMap output on sample repositories. |
| 25 | +- `strategic-compact` — keep long agent sessions manageable. |
| 26 | +- `agent-introspection-debugging` — recover when the agent loops or gets stuck. |
| 27 | + |
| 28 | +## Personal Development Documentation |
| 29 | + |
| 30 | +Keep the private development notes under `docs/for-me-personal/` current while |
| 31 | +working on DevMap. |
| 32 | + |
| 33 | +- Record completed work, current status, important decisions, and remaining |
| 34 | + tasks in `docs/for-me-personal/PROGRESS.md`. |
| 35 | +- Record the latest development testing commands, prerequisites, expected |
| 36 | + results, manual test flows, and cross-platform verification steps in |
| 37 | + `docs/for-me-personal/TEST.md`. |
| 38 | +- Record meaningful debugging incidents in `docs/for-me-personal/DEBUG.md`, |
| 39 | + including the symptom, root cause, solution, verification, and lesson learned. |
| 40 | + |
| 41 | +Update the relevant document whenever implementation or verification changes |
| 42 | +its contents. Do not duplicate these personal notes into the public `docs/` |
| 43 | +folder unless the information is intended for users or contributors. |
0 commit comments