📥 Requirement Gathering — plain language in, structured scope starts

A team member submits a plain language software request — via a Klient PSA Custom Object record, a Slack message, or a Case. No template. No form. Just the request as they'd naturally describe it. SCOPEY receives it and immediately begins structuring.

💬 Slack — #feature-requests
SarahCan we add a field to the project record that captures the client's preferred contact method?
SCOPEY✅ Idea received. Checking existing features and getting my ❓ clarifying question ready.

❓ One Clarifying Question — before anything is written, ambiguity resolved

Before SCOPEY writes a single word of the requirement, it asks exactly one focused question. Not a requirements workshop. Not a list of questions. One question — targeted at the most critical ambiguity.

💬 Slack — #feature-requests
SCOPEY❓ One question before I write:
Should this field be required or optional — and should it appear on the project creation form, the edit page, or both?
SarahOptional. Both forms — creation and edit.
SCOPEY✅ Got it. Writing the requirement now.

📝 Scope Writing — one request in, one complete scope out

One answer. That's all SCOPEY needed. Now it writes — and it doesn't stop at a title and a sentence. Every scope has four parts: Why it's needed, What it does exactly, What could go wrong, and What it must not break. The person who builds it has no excuses. Neither does the person who reviews it.

📄 SCOPEY — REQ-0047 · Preferred Contact Method Field
Why
PMs need to know how clients want to be reached. Right now it lives in someone's head — or worse, an email no one can find.
What
Optional picklist "Preferred Contact Method" — Email / Phone / Slack / Teams — on both the New Project and Edit Project pages.
What could go wrong
· Field left blank → project saves, no error
· Existing records → field shows empty, not broken
What it must not break
· Existing project layout and page rules stay intact
· No validation rule — this field is never required

📋 Your Requirement Style — your structure, your rules, every time

No two businesses scope work the same way. A software consultancy doesn't write requirements like a product team. A fixed-fee project doesn't need the same sections as a T&M retainer. SCOPEY reads its instructions from the Agentforce Agent Resource — plus specific instructions you write in plain language, directly on the project record. No code. No configuration files. Just tell SCOPEY how you want it to write. That means every project type gets its own output structure. Your sections. Your labels. Your level of detail. SCOPEY follows your style — not a generic template.

📋 Agent Resource — Project Type: Salesforce Implementation
Requirement Style
StructureBusiness Need · Technical Spec · Acceptance Tests · Out of Scope
Detail levelDeveloper-ready — no interpretation needed
Project Type: Discovery Sprint
StructureProblem Statement · Hypothesis · Success Signal
Detail levelLightweight — enough to start, not enough to over-engineer
Each project type gets its own style. SCOPEY reads the instruction and writes accordingly.

🎯 Project and Task Created — requirement written to task, ready to assign

SCOPEY creates the tasks — one per scoped item, linked to the right project — with the full structured scope written directly into the task fields. The task is ready to pick up and work on. The next request can come in immediately — SCOPEY is already free for the next scope.

🎯 Klient PSA — Project & Task Created
Task: Add Preferred Contact Method field to Project record
Status🟢 Ready to Develop
RequirementREQ-0047 — Full Requirements Here
Criteria3 acceptance criteria · all must pass
👉 Review and approve to start development →

👁️ You Review — You Approve

Every Klient AI agent operates under a single principle: humans lead, agents deliver. SCOPEY scopes the work and creates the tasks — but you assign them. You read the scope. You decide who picks it up. You stay in the loop at every step.

The Klient AI Contract
🔒
Bounded by your instructions
Every agent operates within the rules, roles, and permissions you set in Klient PSA. Nothing outside your defined scope.
✅
Nothing ships without your approval
Agents prepare, draft, and surface. You review and approve. The outcome is always yours to confirm.
🏠
Secured on Salesforce
Built on Salesforce Agentforce — the platform your org already trusts. Your data never leaves your org.
Humans lead. Agents deliver.
That's Autonomous Project Delivery — and it starts with you in control.