feat(doc-review, learnings-researcher): tiers, chain grouping, rewrite (#601)
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -23,12 +23,16 @@ tracks:
|
||||
- integration_issue
|
||||
- logic_error
|
||||
knowledge:
|
||||
description: "Best practices, workflow improvements, patterns, and documentation"
|
||||
description: "Practices, patterns, conventions, decisions, workflow improvements, and documentation"
|
||||
problem_types:
|
||||
- best_practice
|
||||
- documentation_gap
|
||||
- workflow_issue
|
||||
- developer_experience
|
||||
- architecture_pattern
|
||||
- design_pattern
|
||||
- tooling_decision
|
||||
- convention
|
||||
|
||||
# --- Fields required by BOTH tracks -----------------------------------------
|
||||
required_fields:
|
||||
@@ -57,7 +61,11 @@ required_fields:
|
||||
- workflow_issue
|
||||
- best_practice
|
||||
- documentation_gap
|
||||
description: "Primary category — determines track (bug vs knowledge)"
|
||||
- architecture_pattern
|
||||
- design_pattern
|
||||
- tooling_decision
|
||||
- convention
|
||||
description: "Primary category — determines track (bug vs knowledge). Prefer the narrowest applicable value; best_practice is the fallback when no narrower knowledge-track value fits."
|
||||
|
||||
component:
|
||||
type: enum
|
||||
|
||||
@@ -16,7 +16,7 @@ The `problem_type` determines which **track** applies. Each track has different
|
||||
| Track | problem_types | Description |
|
||||
|-------|--------------|-------------|
|
||||
| **Bug** | `build_error`, `test_failure`, `runtime_error`, `performance_issue`, `database_issue`, `security_issue`, `ui_bug`, `integration_issue`, `logic_error` | Defects and failures that were diagnosed and fixed |
|
||||
| **Knowledge** | `best_practice`, `documentation_gap`, `workflow_issue`, `developer_experience` | Practices, patterns, workflow improvements, and documentation |
|
||||
| **Knowledge** | `best_practice`, `documentation_gap`, `workflow_issue`, `developer_experience`, `architecture_pattern`, `design_pattern`, `tooling_decision`, `convention` | Practices, patterns, conventions, decisions, workflow improvements, and documentation. Prefer the narrowest applicable value; `best_practice` is the fallback. |
|
||||
|
||||
## Required Fields (both tracks)
|
||||
|
||||
@@ -73,6 +73,10 @@ Docs created before the track system may have `symptoms`/`root_cause`/`resolutio
|
||||
- `workflow_issue` -> `docs/solutions/workflow-issues/`
|
||||
- `best_practice` -> `docs/solutions/best-practices/`
|
||||
- `documentation_gap` -> `docs/solutions/documentation-gaps/`
|
||||
- `architecture_pattern` -> `docs/solutions/architecture-patterns/`
|
||||
- `design_pattern` -> `docs/solutions/design-patterns/`
|
||||
- `tooling_decision` -> `docs/solutions/tooling-decisions/`
|
||||
- `convention` -> `docs/solutions/conventions/`
|
||||
|
||||
## Validation Rules
|
||||
|
||||
|
||||
Reference in New Issue
Block a user