Production Lines
Work Order: {Product Name} for {Client}
Work Order: {Product Name} for {Client}
Order ID: WO-{NNN} Client: {Client Name} Product type: {Product Type} Production line: digital-talent Status: Intake Date: {YYYY-MM-DD}
1. Client Profile
| Field | Value |
|---|---|
| Client | {Client Name (full legal or common name)} |
| Segment | {Industry, size range} |
| Need | {One-sentence problem statement} |
| Domain maturity | {Existing practice, tools, maturity level in the target domain} |
| IT landscape | {Complexity: low / medium / high, homogeneous / heterogeneous} |
| Repository | {Existing tools: LeanIX, Ardoq, Jira, ServiceNow, none, etc.} |
| Language | {Working language for outputs} |
| Documentation | {Documentation platform: Confluence, SharePoint, Notion, etc.} |
| Business process | {Which business process does this talent support?} |
| Business capability | {Which business capability does this talent strengthen?} |
| Key user roles | {Who uses the talent day-to-day? Who consumes its outputs?} |
| AI platform | {Claude Code / Copilot / other -- the runtime environment} |
2. Product Definition
The digital talent will provide the following capabilities:
| # | Capability | Description |
|---|---|---|
| 1 | {Capability name} | {What it does} |
| 2 | {Capability name} | {What it does} |
| 3 | {Capability name} | {What it does} |
Add rows as needed. Minimum 3 capabilities required by the intake quality gate.
3. Deliverable Set
| Artifact | Description |
|---|---|
| CLAUDE.md | Client-specific agent configuration |
| .claude/commands/*.md | Skill commands tailored to client methodology |
| {Add deliverables as identified} | {Description} |
4. Skill Inventory
| # | Skill | File | Category | Description |
|---|---|---|---|---|
| 1 | {Skill name} | {filename.md} | {Category} | {What it does} |
Populated during design (Stage 3). Leave blank at intake.
5. Pattern Selection
Populated during design (Stage 3). See Ada (Agentic Pattern Designer) for pattern catalog.
6. Customization Values
| Dimension | Value |
|---|---|
| Methodology | {Client methodology / framework} |
| Language | {Working language} |
| Repository tool | {Primary repository or data tool} |
| Diagram standard | {ArchiMate, UML, BPMN, none, etc.} |
| Publication target | {Confluence, SharePoint, Notion, etc.} |
| Model selection | {Haiku for X, Sonnet for Y, Opus for Z -- or default} |
| Quality thresholds | {What "good enough" means for this client} |
7. Domain-Specific Intake Questions
Supplement the generic intake questions (Stage 1) with domain-specific questions here. These will be populated based on the product type.
8. Domain-Specific QA Test Cases
Populated during QA planning (Stage 5). Define functional tests, edge case tests, and documentation tests.
9. Build Estimate
| Component | Effort |
|---|---|
| {Phase} | {Estimate} |
| Total | {Range} |
10. Dependencies
| Dependency | Source | Status |
|---|---|---|
| {What is needed} | {Who provides it} | {Available / Pending / Blocked} |
11. Scope Boundaries
In scope:
- {Capability or activity that IS included}
Out of scope:
- {Capability or activity that is NOT included}
Compliance / regulatory constraints:
- {Any constraints on data, decisions, or outputs}
Success criteria:
- 30-day: {What success looks like at 30 days}
- 90-day: {What success looks like at 90 days}