Read AGENTS.md and the authoritative contribution workflow. Use its route and ownership guidance; the contributor does not need to choose a provider, datasource or RFC workflow upfront.
1. Establish the current step
Identify the requested outcome and the existing issue, accepted decisions, RFC or implementation branch. Inspect those records and relevant code before asking questions. State the applicable route, current step and missing maintainer decision. Reuse settled scope and design at each handoff.
Work within the request and existing authorization. A draft-only or review-only request ends with that artifact. An implementation request continues through authorized work once applicable maintainer decisions are settled. Prepare the concrete result before requesting publication permission; reuse authorization already given for the same destination and scope.
2. Prepare the issue when the route needs one
Documentation changes and bug fixes can go directly to a PR. Other code contributions need an accepted issue; comment on it to coordinate the work. Follow the product-team exception for changes within an existing owned area.
Search the repository’s open and closed issues for existing reports and proposals before creating an issue or starting implementation. Reuse a relevant issue; check its outcome and maintainer decisions before proceeding. When its maintainer decision is settled, continue to the needed planning or implementation rather than drafting another proposal.
- Bugfixes: can go directly to a PR without a separate issue or prior maintainer acknowledgement. When reporting a bug, search for an existing report first and add relevant evidence there. If no report matches, use the Bug report form. Establish actual and expected behavior, reproduction or evidence, and relevant version/environment. Link the existing report from the fix PR when available. Record verified findings separately from assumptions.
- Feature: use propose-feature to research and draft the common proposal. Show a concrete problem, proposed UX and checkable acceptance criteria; scale examples to the work and identify unresolved facts.
Follow AGENTS.md privacy rules. File or change a shared issue within publication authorization. Reuse any maintainer decisions already recorded on the issue; discuss additional design there or in the PR when no issue exists.
3. Load only the planning that is needed
Follow CONTRIBUTING for the RFC requirement on new features and the product-team exception. Use create-rfc for the required design, review-rfc for design review, and update-rfc when explicitly asked to reconcile existing implementation evidence. Reuse the issue's accepted behavior and scope.
Developers choose their own implementation and planning approach. Reuse the accepted issue and any RFC for scope and acceptance criteria. An RFC can describe the overarching design and PR sequence; straightforward slices can be tracked on the issue.
4. Implement with the appropriate references
For a bug, inspect the relevant subsystem and add appropriate regression coverage. For documentation or test-only work, inspect the affected material.
For a capability or command change, read capability implementation for placement, backend readiness and the command contract. Carry decisions into the existing planning record rather than producing another mandatory document. Then load:
- Provider implementation for a Cloud product provider, including conditional resource adapters and smoke tests.
- Datasource implementation for a new datasource kind, including shared queries, Explore links, codecs and routing.
- Distribution and gates when resource or datasource wiring, command annotations, or bundled skill coverage changes.
Use the existing subsystem implementation for other changes. Resolve routine choices from repository evidence; ask about unresolved choices that materially change scope or behavior. Preserve CONSTITUTION, DESIGN and architecture rules.
5. Verify and prepare review
Read self-review and apply checks triggered by the actual diff, including incremental fixes. Run AGENTS.md quality checks and relevant domain verification using the built binary. Report failed or unavailable checks with their reason; a test or probe that did not run is not a pass.
RFC reconciliation is a separate requested task. When an issue exists, implementation PRs reference it; the final completing PR closes it. Summarize the change, checks, unresolved assumptions and documented deviations for review.