robbond/rdb-discovery
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(task-022): expand discovery coverage

Browse Source
This commit is contained in:
robbond
2026-06-04 07:42:48 +01:00
parent a0b28e7d8d
commit c72ad6995e
8 changed files with 341 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/discovery-context-mapping.md
+51 -1
View File
@@ -1,6 +1,6 @@
# Discovery-to-Context Mapping
This document defines how answers to the 10 core discovery questions should be transformed into project context files.
This document defines how answers to the 14 core discovery questions should be transformed into project context files.
## Reference: Core Discovery Questions
@@ -16,6 +16,10 @@ This document defines how answers to the 10 core discovery questions should be t
| Q-008 | What must not happen? |
| Q-009 | How will we test it? |
| Q-010 | How will it be deployed? |
| Q-011 | Who owns and directs the project, and what are its organisational goals? |
| Q-012 | What is the technology stack, repository structure, and architecture approach? |
| Q-013 | Where is it hosted, which environments exist, and what are the security requirements? |
| Q-014 | What agent and developer workflow tools, constraints, and guidelines apply? |
## Reference: Target Context Files
@@ -136,6 +140,48 @@ Maps to:
| `context/architecture.md` | `## Deployment Architecture` | Describe the deployment layout, scaling strategy, and process. |
| `context/infrastructure-context.md` | `## CI / CD Pipeline`, `## Hosting`, `## Environments` | Fill in hosting platform, environment details, and pipeline steps from the discovery answer. |
### Q-011 — Who owns and directs the project, and what are its organisational goals?
Maps to:
| Context File | Section | Guidance |
|---|---|---|
| `context/company-context.md` | `## Mission` | Record the organisation's core mission, vision, or strategic goals that relate to this project. If no company-level mission exists, record the team's purpose. |
| `context/project-brief.md` | `## Target Audience` | Restate in project-specific terms — who will use or benefit from the final product? |
### Q-012 — What is the technology stack, repository structure, and architecture approach?
Maps to:
| Context File | Section | Guidance |
|---|---|---|
| `context/development-context.md` | `## Tech Stack` | Extract languages, frameworks, libraries, tooling, and build/test tools. Record each as a distinct item. |
| `context/development-context.md` | `## Coding Standards` | Note any style conventions, naming patterns, linters, formatters, or agreed-upon patterns. If none exist, note "TBD". |
| `context/architecture.md` | `## Overview` | Record high-level design principles, architectural patterns (e.g., monolith, microservices), and key design decisions. |
| `context/architecture.md` | `## Core Components` | List the main modules, services, or packages and their responsibilities. Use bullet points for each component. |
### Q-013 — Where is it hosted, which environments exist, and what are the security requirements?
Maps to:
| Context File | Section | Guidance |
|---|---|---|
| `context/infrastructure-context.md` | `## Hosting` | Record hosting platform (cloud provider, on-prem, container orchestration, etc.). |
| `context/infrastructure-context.md` | `## Environments` | List all environments (dev/staging/prod), their purpose, and data management approach. |
| `context/infrastructure-context.md` | `## Monitoring & Alerting` | Document monitoring tools, alerting channels, and observability requirements. |
| `context/infrastructure-context.md` | `## Security` | Record authentication models, data protection requirements, compliance needs, and access control policies. |
### Q-014 — What agent and developer workflow tools, constraints, and guidelines apply?
Maps to:
| Context File | Section | Guidance |
|---|---|---|
| `context/agent-guidelines.md` | `## Purpose` | Record why agents need specific context for this project (constraints, conventions, expectations). |
| `context/agent-guidelines.md` | `## Preferred Tools` | List recommended editors, debuggers, testing frameworks, CLI tools, and automation tools. |
| `context/repository-context.md` | `## Purpose` | Record the project's overall purpose, scope boundaries, and what it is / is not responsible for. |
| `context/repository-context.md` | `## Contributing` | Document contribution process, branch strategy, code review requirements, and testing expectations for contributors. |
## Summary: Question-to-File Matrix
This matrix provides a quick-reference view of all mappings. "Primary" means the answer should go there first; "Secondary" means it may also be updated if relevant.
@@ -152,6 +198,10 @@ This matrix provides a quick-reference view of all mappings. "Primary" means the
| Q-008 | What must not happen? | assumptions.md, decisions.md | open-questions.md |
| Q-009 | How will we test it? | development-context.md, TEST_PLAN.md | — |
| Q-010 | How will it be deployed? | architecture.md, infrastructure-context.md | — |
| Q-011 | Who owns and directs the project? What are its organisational goals? | company-context.md, project-brief.md | — |
| Q-012 | What is the technology stack, repository structure, architecture approach? | development-context.md, architecture.md | — |
| Q-013 | Where is it hosted, which environments exist, and what are the security requirements? | infrastructure-context.md | — |
| Q-014 | What agent and developer workflow tools, constraints, and guidelines apply? | agent-guidelines.md, repository-context.md | — |
## Implementation Notes for Future Work