Official recipe

Map ERP requirements to a costed implementation sequence

Estimates can conceal unsupported scope and cycles.

Read original recipe

Proposed inputs

Name
Requirement list
Owner
Customer representative
Minimum scope
A short numbered list stripped of confidential details
Quality check
Preserve identifiers and wording.
Name
Evidence packet
Owner
Technical owner
Minimum scope
Version-labelled source findings
Quality check
Missing evidence remains unknown.
Name
Estimating assumptions
Owner
Commercial owner
Minimum scope
Approved rates and exclusions
Quality check
No invented or duplicated adjustments.

Access and setup — proposed or unknown

Proposed minimum: Start with supplied fictional source results and an offline worksheet.
Keep evidence review and commercial approval as distinct decisions.
Compatibility unknowns: Unknown: indexed profile coverage, source freshness and hosted or self-hosted access.
Unknown: whether static source behavior matches the intended deployment.
External actions requiring approval: Sending real requirements to a third party or presenting estimates as an approved proposal.

Detailed steps and output format

At a glance

Suggested result: Requirements matrix, estimate and dependency exceptions.Suggested; untested.
Tool: Claude Code; Odoo Semantic MCPSource-named; check current access.
Suggested inputs: Requirement list; Evidence packet; Estimating assumptionsProposed; access notes below.
Human review: Approve real-data access and installed components separately. Review proposed outputs before any live change, transmission or public use.Suggested boundaries; source approvals below.
Setup notes: Start with supplied fictional source results and an offline worksheet. Keep evidence review and commercial approval as distinct decisions.Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Function and scope

Operations, Finance · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Estimates can conceal unsupported scope and cycles.

Suggested task · untested

Proposed: prepare a traceable, costed implementation sequence.

What you could produce

Requirements matrix, estimate and dependency exceptions.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Proposed guidance and fictional tests; source-shaped procedures remain attributed to the linked original. No execution is claimed.

Read the attributed source evidence and original caveats below ↓

Why use this

Feature availability varies by edition and version.
Traceability exposes unsupported scope.

Why an agent / simpler alternative

Useful judgment: Interpret requirements against available evidence.
Simpler alternative: Use a fixed estimating sheet for a repeated, already verified configuration.
Unsuitable when: The requested version or cost assumptions are unknown, or the source evidence cannot be checked.

Expected deliverable and review checks

Proposed artifact: Requirements matrix, estimate and dependency exceptions.
Critical checks: Keep every requirement; reconcile costs; expose unknowns and cycles.
Missing output evidence: Unknown: no completed matrix, current index coverage or estimate accuracy was independently verified.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Six fictional requirements include one missing source result and a cycle between R-04 and R-05. A made-up rate card is 100 units per day; the supplied effort bands total 8–12 days, with no contingency authorized.
Acceptance checks: Six rows; missing evidence unverified.
Return 800–1,200 units; no contingency.
Expose R-04/R-05 cycle; withhold feasibility.
Stop conditions: Real pricing or confidential customer material is introduced.
An unverified requirement is presented as supported or an estimate becomes a commitment.

Tasks: Writing & content

Useful for: General use

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Claude Code; Odoo Semantic MCPIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Unsupported capability classification.
Why it matters
Scope may be false.
Proposed response
Mark unverified.
Signal
Circular prerequisites.
Why it matters
Sequence is infeasible.
Proposed response
Expose cycle for owner resolution.

Effort and cost — unknown

Setup work: Agree evidence and rates.
Ongoing review: Review unknowns and dependencies.
Unknowns: Unknown: model usage, index-access terms and exception-review workload.

Limits

Static evidence cannot establish deployment or commercial viability.

Full source evidence

Official recipe · Tool workflows

Original task title: Map ERP requirements to a costed implementation sequence

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://github.com/Viindoo/odoo-mcp-client/blob/master/plugins/odoo-ai-agents/skills/odoo-brl/SKILL.md ↗

Attributed to: Viindoo repository maintainers

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.