implementation-requirements-extractor
Agent: Implementation Engineer
L2 implementation engineer (Nx, multi-instance) responsible for extracting customer requirements and running technical onboarding.
Department ethos: ideal-implementation.md
Tool policy: allowed-tools.yaml
Skill Description
The implementation requirements extractor conducts structured discovery sessions with new customers to capture their technical environment, business workflows, integration needs, and success criteria before implementation work begins.
When to Use
- When a new customer deal is signed and implementation needs to begin with a clear scope.
- When a sales handoff includes vague or incomplete requirements that need detailed technical discovery.
- When an existing customer purchases additional products or modules that require a new implementation scope.
- When implementation has started but keeps encountering undocumented requirements that cause rework.
Workflow
- Review the sales handoff: Read the deal notes, SOW, and any pre-sales technical assessments to understand what was sold and promised. Deliverable: sales context summary.
- Prepare discovery questions: Build a structured questionnaire covering technical environment, data sources, integrations, workflows, users, and success criteria. Deliverable: discovery questionnaire.
- Conduct discovery sessions: Run sessions with the customer's technical and business stakeholders to capture requirements. Deliverable: session notes and recordings.
- Document requirements: Compile findings into a structured requirements document covering functional, technical, integration, data migration, and acceptance criteria. Deliverable: requirements document.
- Validate with the customer: Review the requirements document with the customer to confirm accuracy and completeness, and obtain sign-off. Deliverable: customer-validated requirements with sign-off.
Anti-Patterns
- Skipping sales handoff review: Starting discovery without reading what was sold and promised. Why: missing sales context leads to requirements that contradict the SOW, creating scope disputes.
- Technical-only discovery: Extracting technical requirements without understanding the business workflows they support. Why: technically correct implementations that do not match business workflows fail user adoption.
- Requirements without sign-off: Proceeding with implementation based on verbal requirements. Why: unsigned requirements invite scope creep and disputes about what was agreed.
Output
On success: A customer-validated requirements document covering functional, technical, integration, and data migration requirements, with acceptance criteria and customer sign-off.
On failure: Report which requirement areas are incomplete (e.g., customer could not provide data schema, security team unavailable), what was captured, and recommend follow-up sessions with specific stakeholders.
Related Skills
1---2name: implementation-requirements-extractor3description: This skill extracts and documents the technical and business requirements from new customers before implementation begins. Use when asked to gather customer requirements, run discovery sessions, or document implementation scope. Also consider when a signed deal is handed off from sales. Suggest when implementation is about to begin without documented requirements.4---56# implementation-requirements-extractor78## Agent: Implementation Engineer910L2 implementation engineer (Nx, multi-instance) responsible for extracting customer requirements and running technical onboarding.1112Department ethos: [ideal-implementation.md](../../../../departments/implementation/ideal-implementation.md)13Tool policy: [allowed-tools.yaml](../../../../allowed-tools.yaml)1415## Skill Description1617The implementation requirements extractor conducts structured discovery sessions with new customers to capture their technical environment, business workflows, integration needs, and success criteria before implementation work begins.1819## When to Use2021- When a new customer deal is signed and implementation needs to begin with a clear scope.22- When a sales handoff includes vague or incomplete requirements that need detailed technical discovery.23- When an existing customer purchases additional products or modules that require a new implementation scope.24- When implementation has started but keeps encountering undocumented requirements that cause rework.2526## Workflow27281. **Review the sales handoff**: Read the deal notes, SOW, and any pre-sales technical assessments to understand what was sold and promised. Deliverable: sales context summary.292. **Prepare discovery questions**: Build a structured questionnaire covering technical environment, data sources, integrations, workflows, users, and success criteria. Deliverable: discovery questionnaire.303. **Conduct discovery sessions**: Run sessions with the customer's technical and business stakeholders to capture requirements. Deliverable: session notes and recordings.314. **Document requirements**: Compile findings into a structured requirements document covering functional, technical, integration, data migration, and acceptance criteria. Deliverable: requirements document.325. **Validate with the customer**: Review the requirements document with the customer to confirm accuracy and completeness, and obtain sign-off. Deliverable: customer-validated requirements with sign-off.3334## Anti-Patterns3536- **Skipping sales handoff review**: Starting discovery without reading what was sold and promised. *Why*: missing sales context leads to requirements that contradict the SOW, creating scope disputes.37- **Technical-only discovery**: Extracting technical requirements without understanding the business workflows they support. *Why*: technically correct implementations that do not match business workflows fail user adoption.38- **Requirements without sign-off**: Proceeding with implementation based on verbal requirements. *Why*: unsigned requirements invite scope creep and disputes about what was agreed.3940## Output4142**On success**: A customer-validated requirements document covering functional, technical, integration, and data migration requirements, with acceptance criteria and customer sign-off.4344**On failure**: Report which requirement areas are incomplete (e.g., customer could not provide data schema, security team unavailable), what was captured, and recommend follow-up sessions with specific stakeholders.4546## Related Skills4748- [`implementation-playbook-builder`](../../../implementation/implementation-lead/implementation-playbook-builder/SKILL.md) -- the playbook defines the discovery phase that this skill executes.49- [`technical-onboarding-runner`](../technical-onboarding-runner/SKILL.md) -- onboarding uses the extracted requirements to configure the customer's environment.50- [`integration-catalogue-builder`](../../../implementation/implementation-lead/integration-catalogue-builder/SKILL.md) -- the integration catalogue informs which integrations to probe during discovery.
mittuled