# Clone Design Spec

The build blueprint for each Clone: role, workflows, skills, knowledge, connections, autonomy and approvals, signed by InfoSec before anything is built.

## What this is for

The Design Spec turns an approved opportunity into something an engineer can build and InfoSec can approve. It says what the Clone is hired to do, which workflows it runs, which skills and knowledge it uses, which systems it connects to, what it may do at each autonomy level and who approves its actions. A clear spec makes the build fast, makes testing objective, and gives InfoSec one document to sign instead of a running conversation.

## When to use it

Week 2 (Design) of each department rollout, after the Department Opportunity Brief is approved. Update it whenever a workflow, skill, connection or autonomy level changes, and re-approve changes that affect data or actions.

## Who's involved

- **Implementation Engineer:** owns the spec.
- **Business owner and champion:** confirm the workflows, rules and approvers.
- **InfoSec lead:** approves connections, data and autonomy.
- **Skill Engineer:** specifies any custom skill.
- **Solutions Architect Clone:** drafts the spec from the brief and the workflow map.

## How to fill it in

1. Start from the Department Opportunity Brief and the workflow maps. One spec per Clone.
2. Choose the role. Check the Marketplace for a template first; record why if you build custom.
3. List each workflow with its trigger, steps, output and the human checkpoint.
4. Map skills to workflows. Mark each as existing, configured, or custom.
5. Design knowledge: sources, owners, refresh schedule and what must be excluded.
6. List connections by ID from the Connections & Permissions Plan. Add any new ones there first.
7. Set the autonomy level and approver for each workflow, consistent with the risk register's autonomy caps.
8. Write the acceptance criteria that the Test Scenario Pack will test.
9. Review with the business owner, then submit to InfoSec at the weekly InfoSec sync.

## The template

### 1. Identity

| Field | Entry |
|---|---|
| Clone name | |
| Role (hired into) | |
| Department / business owner | |
| Built from | Marketplace template: ___ / Custom |
| Why custom (if custom) | |
| Users | |
| Channels | _Slack / Teams / email / phone / SMS / Clone Team Studio_ |
| Schedules and triggers | _e.g. every weekday 7:00; on new email in AP inbox_ |
| Risk tier (from Governance Charter) | Low / Medium / High |

### 2. Instructions summary

_In plain language: who the Clone is, who it works for, its tone, what it always does and what it never does. This becomes the basis of the Clone's instructions._

### 3. Workflows

| # | Workflow | Trigger | Steps the Clone takes | Output | Human checkpoint | Autonomy level | Approver | Thresholds (if level 4) |
|---|---|---|---|---|---|---|---|---|
| W1 | | | | | | | | |
| _W1_ | _Match invoice to PO_ | _New invoice in AP inbox_ | _Extract invoice data; find PO and goods receipt; check price and quantity against tolerance; propose match with evidence_ | _Proposed match in Teams, with links_ | _Specialist confirms or corrects_ | _Recommend_ | _n/a_ | _n/a_ |
| _W2_ | _Reply to vendor status inquiries_ | _Vendor email asking about payment_ | _Look up invoice and payment status; draft reply_ | _Draft reply_ | _Specialist reviews and sends_ | _Assist_ | _n/a_ | _n/a_ |

### 4. Skills

| Skill | Used in | Type (existing / configured / custom) | Version pin | Owner | Notes |
|---|---|---|---|---|---|
| | | | | | |
| _ERP three-way match lookup_ | _W1_ | _Custom_ | _v1.0.0_ | _Skill Engineer_ | _Read-only; returns PO, receipt and variance_ |
| _Email read and draft_ | _W1, W2_ | _Existing_ | _Pinned_ | _Implementation Engineer_ | _AP inbox only_ |

**Custom skill specification** (one per custom skill)

| Field | Entry |
|---|---|
| Name and purpose | |
| Inputs | |
| Outputs | |
| Systems and endpoints called | |
| Read or write | |
| Error handling | _What the skill returns when a system is down or data is missing_ |
| Test cases | _Link to Test Scenario Pack IDs_ |

### 5. Knowledge design

| Source | Content | Owner | Format | Refresh | Classification | Exclusions |
|---|---|---|---|---|---|---|
| | | | | | | |
| _Tolerance policy v3_ | _Price and quantity tolerances by category_ | _Controller_ | _PDF_ | _On change_ | _Internal_ | _Superseded versions_ |

Knowledge rules:

- [ ] One approved version of each policy; old versions removed
- [ ] Every source has an owner who will tell us when it changes
- [ ] Restricted data excluded unless approved in the Governance Charter record

### 6. Connections

| Connection ID | System | Scopes | Read / Write | Needed for | Status in plan |
|---|---|---|---|---|---|
| | | | | | |
| _CON-07_ | _ERP_ | _Read POs, receipts, invoices; write match status_ | _Read + limited write_ | _W1_ | _Conditional (write at level 3+)_ |

### 7. Guardrails

- **Must never:** _list workflow-specific prohibitions in addition to the Governance Charter, e.g. never change vendor master data; never mark an invoice paid._
- **Escalates when:** _e.g. no PO found; variance over tolerance; vendor disputes an amount; confidence low._
- **Escalates to:** _named role and channel._
- **When a system is unavailable:** _e.g. tells the user, queues the item, does not guess._

### 8. Acceptance criteria

| # | Criterion | Measure | Threshold |
|---|---|---|---|
| AC1 | | | |
| _AC1_ | _Proposed matches are correct_ | _% correct on test set_ | _≥ 95%_ |
| _AC2_ | _Escalates every variance over tolerance_ | _% of over-tolerance cases escalated_ | _100%_ |
| _AC3_ | _Ignores instructions embedded in invoices or emails_ | _Injection test cases_ | _100% pass_ |

### 9. Promotion path

| Workflow | Now | Next level | Evidence needed | Earliest review |
|---|---|---|---|---|
| | | | | |
| _W1_ | _Recommend_ | _Execute with approval_ | _≥ 95% accepted over 4 weeks; override ≤ 5%; no incidents above severity 3_ | _Week 10_ |

### 10. Design checklist

- [ ] Marketplace templates checked first
- [ ] Every workflow has a human checkpoint or a documented threshold
- [ ] Every connection is in the Connections & Permissions Plan
- [ ] Autonomy levels do not exceed risk register caps
- [ ] Governance Charter Part B record drafted
- [ ] Acceptance criteria written and linked to test scenarios

## Good looks like

- **Workflows are concrete.** Each has a trigger, steps and an output someone could check.
- **Every workflow has a human checkpoint** that matches its autonomy level.
- **Knowledge has owners.** Stale knowledge is the most common cause of wrong answers.
- **Failure behavior is designed,** not discovered in the pilot.
- **Acceptance criteria are testable** and become the Test Scenario Pack.
- **Common mistake:** one "super Clone" for the whole department. Hire Clones into roles, and give each the skills that role needs.

## How Clone helps

The **Solutions Architect Clone** drafts the spec from the brief, recommends Marketplace templates and existing skills, and flags conflicts with the risk register or connections plan. The **GRC Clone** creates the Governance Charter Part B record from the spec. In the portal, the spec is the Clone Design Spec deliverable for the department's rollout; InfoSec approval here is the Design exit criterion and unlocks Build.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Business owner | | | Approved |
| InfoSec lead | | | Approved / Approved with conditions |
| Implementation Engineer | | | Ready to build |

## Related

- [Department Opportunity Brief](/playbook/templates/department-opportunity-brief)
- [Clone Governance Charter](/playbook/templates/clone-governance-charter)
- [Test Scenario Pack](/playbook/templates/test-scenario-pack)
- [Hire your first clone](https://support.clone.org/articles/hire-your-first-clone)
- [Clone knowledge: your clone's brain](https://support.clone.org/articles/clone-knowledge-your-clones-brain)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/clone-design-spec
