What Is Solutioneer

Solutioneer is a skill pack — a bundle of narrow, opinionated workflows that run inside Codex. It is not a chatbot, not a web app, and not an agent framework. It is a set of rules and templates that make Codex useful for pre-sales and solution engineering work in a predictable way.

The skill-pack model

Each skill is a folder under skills/ with two files:

• A SKILL.md containing the trigger conditions, intake order, execution rules, provider rules, output shape, and save/writeback rules.
• A manifest.json declaring the inputs, expected outputs, Firecrawl modes, Composio toolkits, and Composio tool slugs the skill can use.

When you invoke a skill, Codex loads the SKILL.md into context and follows its rules. There is no separate runtime; the rules are the runtime.

What Solutioneer does

• Runs eight fixed skills: account-intel-brief, discovery-context-ingester, discovery-question-generator, demo-scenario-builder, architecture-fit-mapper, integration-fit-gap-analyzer, poc-handoff-orchestrator, and security-review-prep.
• Enforces one-question intake — you are never asked to hand over a filled JSON blob.
• Normalizes chat into a shared input shape (SkillRunInput in tools/core/types.ts).
• Calls Firecrawl wrappers for grounded research and Composio wrappers for external writeback, but only through the repo-local helpers.
• Returns a markdown artifact in chat with a citations or assumptions section.

What Solutioneer does not do

• It does not invent account facts, vendor claims, integration support claims, or product and security assertions. Anything not grounded is labelled as an assumption or unknown.
• It does not save files by default.
• It does not push to Google Docs, Confluence, Linear, or GitHub by default.
• It does not silently execute external tools. Writebacks require an explicit destination confirmation and a connected Composio toolkit.

The runtime guarantees

Three guarantees are load-bearing and every skill page will refer back to them:

1. Default disposition is chat-only. No files. No external calls that change state.
2. Missing keys degrade gracefully. Without FIRECRAWL_API_KEY, research stays local and claims must be labelled. Without COMPOSIO_API_KEY, external writeback is disabled and the artifact is still returned in chat.
3. Connect-now gating. When an external write is requested, Codex checks whether the required toolkit is connected. If it is not, you see a Connect now / Skip decision point before any write happens.

Everything else — the sidebar structure, the output shape of each skill, the list of Composio toolkits — is downstream of these three.