Ideas & Exploration
Completed
- Tool marketplace design #medium
- Tool search and filtering #medium
- User tool ratings/reviews #low
- Tool composition and chaining #medium
- Tool testing framework #medium
- Provider auto-detection #low
- Tool templates/scaffolding (wizards + guided creation) #medium
- MCP client + server integration
- Agent Skills standard (SKILL.md + per-provider skills)
- Tool contracts (input_schema / output_schema)
- Deterministic contract conformance testing
- Registry-aware cf picker
Future Ideas
Live evaluation
Run a tool with multiple real providers and compare outputs. Feed results into the quality scoring engine. Tells users which provider works best for each tool.
Parallel step execution
Run independent steps concurrently. The contract system knows which steps depend on which variables — auto-parallelize to cut wall-clock time.
Contract-driven composition
When building a tool, suggest downstream tools whose input contracts match the current tool's output contract. Surface compatible tools from local and registry.
Conditional routing
Declarative step routing based on output properties (e.g., "if confidence is low, retry with a more capable provider") without writing Python logic.
Issue-based improvement loop
cf --issue "description" captures tool name, version, input size, execution
time, and error output into ~/.cmdforge/<tool>/issues/. The improvement
engine (M9.2) correlates issues with scrutiny findings and suggests specific
fixes. Reviewable via cmdforge review <tool>.