feat: support role-based agent prompts

TASKS.md

@@ -282,34 +282,129 @@ Acceptance Criteria:
 - Keep templates simple markdown
 - Add/update tests
 
-## TASK-017 — Generate context files from discovery answers
+## TASK-017 — Support task roles in generated prompts
 
-Status: Todo
+Status: Done
 
 Goal:
-Use captured discovery answers to generate initial context files.
+Allow tasks to define the agent role used by `rdb prompt`.
 
 Implementation Gap:
 
-Discovery questions can collect information, but the answers are not yet transformed into structured project context documents.
+Tasks can now include a `Role:` field, but `rdb prompt` still always generates prompts beginning with `You are an implementation agent.`
+
+Acceptance Criteria:
+
+- Parse optional `Role:` field from task markdown
+- If `Role:` exists, use it in the generated prompt opening
+- If `Role:` is missing, default to `Implementation Agent`
+- Add/update tests
+- Do not change task execution behaviour
+
+Definition of Done:
+
+- `Role: Architecture Agent` generates `You are an architecture agent.`
+- Tasks without a role still generate implementation prompts
+- Tests pass
+
+## TASK-018 — Role-based context selection
+
+Status: Todo
+
+Role: Implementation Agent
+
+Goal:
+
+Allow `rdb prompt` to select different context files based on task role.
+
+Implementation Gap:
+
+Tasks can now define a role, but every generated prompt still asks the agent to read the same set of files regardless of task type.
+
+Acceptance Criteria:
+
+- Architecture Agent receives architecture-focused context
+- Implementation Agent receives implementation-focused context
+- Documentation Agent receives documentation-focused context
+- If no role exists, use current default file list
+- Add/update tests
+
+Definition of Done:
+
+- Context files differ by role
+- Existing prompts remain backward compatible
+- Tests pass
+
+## TASK-019 — Define discovery-to-context mappings
+
+Status: Todo
+
+Role: Architecture Agent
+
+Goal:
+
+Define how discovery answers should be transformed into project context files.
+
+Implementation Gap:
+
+Discovery answers are collected and stored, but there is no documented mapping between discovery questions and the context files they should populate.
+
+Acceptance Criteria:
+
+- Every discovery question maps to one or more context files
+- Every discovery question maps to a specific section within those files
+- Mapping is documented in markdown
+- Mapping is understandable by future agents
+- No context generation implementation yet
+- Add/update tests if required
+
+Definition of Done:
+
+- Mapping document exists
+- Mapping covers all discovery questions
+- Future implementation work is clearly defined
+
+## TASK-020 — Generate context files from discovery answers
+
+Status: Todo
+
+Role: Implementation Agent
+
+Goal:
+
+Generate initial context files using the approved discovery-to-context mapping.
+
+Implementation Gap:
+
+Discovery answers can be collected, but they are not yet transformed into structured project documentation.
 
 Acceptance Criteria:
 
 - Add command or function to generate context files from discovery data
+- Use the approved mapping document
 - Create missing context files safely
 - Do not overwrite existing files without explicit behaviour
 - Add/update tests
 
-## TASK-018 — Add context completeness report
+Definition of Done:
+
+- Context files can be generated from discovery data
+- Existing files are preserved
+- Tests pass
+
+## TASK-021 — Add context completeness report
 
 Status: Todo
 
+Role: Implementation Agent
+
 Goal:
+
 Report which expected context files exist and which sections still need information.
 
 Implementation Gap:
 
-There is no way to see whether a project has enough context for an AI agent to work effectively.
+There is no way to determine whether a project has sufficient context for effective AI-assisted development.
 
 Acceptance Criteria:
 
@@ -319,15 +414,34 @@ Acceptance Criteria:
 - Report obvious placeholder sections still needing completion
 - Add/update tests
 
-## TASK-019 — Generate Claude Code permission profile
+Definition of Done:
+
+- Context report command exists
+- Missing context is reported clearly
+- Tests pass
+
+## TASK-022 — Generate Claude Code permission profile
 
 Status: Todo
 
+Role: Documentation Agent
+
 Goal:
+
 Create a recommended Claude Code permissions configuration for RDB workflows.
 
+Implementation Gap:
+
+Claude Code permission settings are not currently documented, resulting in unnecessary approval prompts and inconsistent behaviour between projects.
+
 Acceptance Criteria:
 
-- Safe commands auto-approved
-- Dangerous commands require approval
-- Profile documented in CLAUDE.md
+- Define recommended safe commands for auto-approval
+- Define commands that should require approval
+- Document the profile in CLAUDE.md
+- Include rationale for each category
+
+Definition of Done:
+
+- Permission profile documented
+- CLAUDE.md updated