Updating Feature Context from Feedback
Quick start
Collect or infer:
- •Existing context pack (or path to it)
- •Feedback source (user research, support tickets, analytics, PM input)
- •Feedback type (gap, correction, expansion, deprecation)
- •Change scope (additive, modifying, removing)
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Load the existing context pack and identify its current version.
- •Categorize incoming feedback using the feedback taxonomy.
- •Map each feedback item to affected context sections (vocabulary, states, actions, constraints).
- •Draft proposed changes with explicit before/after deltas.
- •Flag conflicts where feedback contradicts existing context or other feedback.
- •Generate a change summary with rationale for each modification.
- •Update version metadata and changelog.
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Default: Low. Context changes must be traceable and justified.
- •Allowed variation: Rationale phrasing and changelog format may adapt to team conventions, as long as traceability is preserved and rubric passes.
Failure modes to avoid
- •Applying feedback without validating source credibility
- •Overwriting context without preserving change history
- •Conflating user requests with validated needs
- •Introducing terminology conflicts with existing vocabulary
- •Removing states without confirming deprecation across all touchpoints
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md
- •Feedback taxonomy: reference/feedback-taxonomy.md
- •Change record schema: reference/change-record-schema.md