code-review-intent

Generate design intent documentation by providing a work brief and your feature branch git diff. The Skill extracts design context, tradeoffs, and excluded scope to align reviewers and workers prior to PR submission.

Documenting the reasoning behind code changes requires capturing work requirements, design decisions, and tradeoffs. This Skill standardizes that process by extracting context directly from work briefs and diffs into a shared document.

Yes, ambiguity flagging identifies unclear or unconfirmed design choices during document generation. It compiles a list of open questions for stakeholder clarification before you finalize the intent document and submit the PR.

Design intent documentation works specifically for feature branch workflows. Technical leads use it to document branch design decisions, tradeoffs, and excluded scope, ensuring both workers and reviewers understand implementation choices.

Provide your work brief and the git diff for your current feature branch. The Skill analyzes these inputs to output a standardized design intent document to a predefined artifact path, eliminating manual writing effort.

A work brief outlines requirements, but design intent documentation captures implementation reasoning, tradeoffs, and excluded scope. It bridges the gap between briefs and code, reducing redundant discussions during code review.