microsoft / microsoft/hve-core

docs(agents): document orientation-first mode in user-facing docs and code-review skill

Open Beginner friendly
#2,092 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agents feature needs-triage
Dominant language
Python
Stars
1.5k
Forks
301
Avg merge
3d 3h
Merged PRs (30d)
92

Description

Tracks WI-04 from the orientation-first review integration epic (#2090).

The orientation-first review mode introduced by Scenario D needs to be surfaced in user-facing documentation and the HVE getting-started guide so contributors know the loop exists and how to use it.

Acceptance criteria:

  • The HVE guide references the orientation-first review mode and explains the Scenario D loop at a user-facing level.
  • .github/skills/coding-standards/code-review/SKILL.md is updated to document the walkthrough-protocol and dispatch-loop as user-accessible entry points.
  • Documentation does not require understanding the internal dispatch-manifest.json or diff-state.json contracts.

References:

  • Parent epic: #2090
  • Affected files: HVE getting-started docs, .github/skills/coding-standards/code-review/SKILL.md
    Related to #2090

Generated by Issue Triage for issue #2090 · 70.8 AIC · ⌖ 13.1 AIC · ⊞ 28.5K ·

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the HVE getting-started docs and .github/skills/coding-standards/code-review/SKILL.md. Document the orientation-first review mode and Scenario D loop for users, including the walkthrough-protocol and dispatch-loop as entry points. Done means both locations explain how to use the loop without requiring knowledge of dispatch-manifest.json or diff-state.json.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
75/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.