Fde opportunity map
Skill wakqasahmed/agentic-commerce-skills/skills/agentic-commerce/fde-opportunity-map
Canonical agentic commerce skills, aggregated by wakqasahmed/skills
npx -y skills add wakqasahmed/agentic-commerce-skills --skill fde-opportunity-mapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Identify when an ecommerce prospect needs Forward Deployed Engineering beyond a standard custom-agent setup.
SKILL.md
1.4 KB, as published. Nobody here has run it
FDE Opportunity Map
Workflow
- Look for custom platform, ERP, PIM, OMS, support, feed, checkout, protocol, or workflow integration needs.
- Separate configuration work from engineering delivery.
- Identify dependencies, data contracts, approval gates, and operational risk.
- Propose a small FDE sprint with clear outcome and verification.
Run the checks in references/checks.md against the proposed integration inventory before sizing an FDE sprint.
Output
- Integration/workflow need
- Why custom-agent setup alone is insufficient
- Required systems and owners
- Smallest useful FDE scope
- Verification and rollback path
Guardrails
- See
../references/guardrails.mdfor shared cross-skill guardrails (autonomous action safety, evidence provenance, internal runtime disclosure). - Recommend FDE only when a verified custom integration or workflow constraint exceeds configuration of the standard custom-agent setup.
- Do not present a discovery finding as an approved integration, data contract, production access, or authorization to change an operational system.
- Define the smallest reversible sprint with named system owners, approval gates, success evidence, and a rollback path before proposing delivery.