Pull request
See the implementation, relevant decisions and testing notes in the code review path your team already uses.
EXISTING PRODUCTS / 03
Ship into the product you already have.
Connect to the codebase and product context you already own, orient around its real constraints, and choose a first request that produces a useful, reviewable result.
EXISTING PRODUCT DELIVERY PATH
CONNECT → ORIENT → FIRST REQUEST → BUILD → PR → PREVIEW → APPROVE → PRODUCTION
01 / CONNECT
Safe access, through the system that owns it.
Repository, deployment, design and observability access should be granted through their native invitation or secret-management paths. Credentials do not belong in task text or file uploads.
02 / ORIENT
Read the product before changing it.
Orientation covers architecture, conventions, delivery checks, environments, product language and known constraints. The goal is useful context, not a month of passive discovery.
03 / FIRST REQUEST
Choose a real outcome with a contained edge.
The first request should matter and still have a clear review surface. It validates the complete path from context to pull request, preview, approval and production.
THE REVIEW SURFACE
Inspect the change where it actually lives.
Preview
Use a safe non-production surface to inspect interaction, responsive behavior and realistic product states where available.
Production
Release only after the required approval and checks. Client-owned infrastructure stays client-owned throughout.
WORKING BOUNDARIES
Momentum without pretending dependencies do not exist.
If a request is waiting on unavailable access, an external vendor or a client decision, the blocker is recorded. The active slot may be released for another ready request rather than remaining artificially occupied.
Changes respect the existing product’s review, test and release controls. If the product lacks a safe path for the requested outcome, establishing that path may become the first scoped request.
GOOD FIRST REQUESTS
Contained enough to learn. Useful enough to count.
- FeatureAdd a complete, bounded user action with acceptance criteria.
- BugReproduce and remove a specific production defect with regression coverage.
- FlowImprove a high-friction interaction across design and implementation.
- IntegrationConnect one external capability with explicit failure behavior.
NEXT / INTAKE
Show the product. Name the next outcome.
Send the outcome, the context you have and what done should look like. The first response stays written and practical.
Send a task first →
No sales call. No commitment.