Bulk invitation flow — ready for reviewEditable interface design · desktop state
TEAM SETTINGSInvite team members
Design approved- 1Upload
- 2Review
- 3Send
PersonRoleStatus
FOFinance Ops[email protected]Admin⌄
Product workflow launchTurn an operations request into
Turn an operations request into
a tested product workflow.
Keep the PRD, existing repository, design system, and acceptance criteria in one project. UIDesigner makes the interaction states reviewable first; ProductDeveloper then implements and verifies the same accepted behavior.
- Start with
- A PRD, issue, bug report, design, or explicit acceptance criteria
- Finish with
- An approved interface, focused code change, and acceptance evidence
UIDesigner produces a reviewable bulk-invitation interface with duplicate and permission states. ProductDeveloper implements the approved design and verifies its acceptance criteria.
Follow along
Implement a product workflow
Copy it, paste it into the Orkas input box, and start trying it.
Example request
Add bulk member invitations with duplicate detection and clear permission errors. Keep the existing single-invite flow working, add tests for every acceptance criterion, and return the files changed plus any item you could not verify.
What you receive
Design, implementation, and verification in one review trail
The team can inspect the approved interface states, focused patch, and acceptance evidence without reconstructing the work.
Reviewable interface states
An editable interface artifact covering the happy path, duplicates, permission errors, and keyboard flow.
bulk-invitation-design.htmlFocused implementation
A narrow repository change that preserves the existing single-invite behavior.
invitation-workflow.patchAcceptance evidence
A criterion-by-criterion result with tested states, regressions, and any unresolved item.
acceptance-test-report.mdDetailed process
Map first, change narrowly, verify every acceptance point
Provide the requirement
Start from a PRD, issue, bug report, design, or explicit acceptance criteria.
Map the repository
Identify relevant code paths, tests, constraints, and risk before editing.
Implement the focused change
Keep the patch coherent and avoid unrelated cleanup that makes review harder.
Verify acceptance
Return tests, review evidence, measured results, and clearly marked unverified items.
Start this work
Download Orkas — freeTry this use case in Orkas
Free, open source, and runs on your machine.
FAQ
Product development questions
Common answers about repository work, review evidence, and production boundaries.
What work can ProductDeveloper handle?
Feature implementation, bug and CI repair, test repair, focused refactors, code review, and performance debugging from a PRD, requirement, issue, bug report, or design.
How does it verify acceptance criteria?
Each accepted behavior is mapped to a current targeted test, review result, or measured performance result. Anything not verified is explicitly marked instead of being presented as complete.
How does ProductDeveloper control implementation risk?
It maps the relevant repository paths before editing, keeps the patch focused, and reports architecture, compatibility, migration, and rollback concerns for review.
Which models can ProductDeveloper use?
Use optional Orkas-managed official models or connect OpenAI, Anthropic Claude, Google Gemini, and other providers through OAuth or an API key. Calls using your own provider go directly to it.
Ready when you are
Turn the next requirement into a verified product change
Free, open source, and runs on your machine.