cogni-consult vs. ido4shape

Consulting engagement orchestrator where action fields are the work-breakdown-structure containers for every deliverable: each deliverable runs its own design-thinking loop (empathize→define→ideate→prototype→test), acting stakeholder personas challenge the work in their own voice, and one cogni-knowledge base per engagement is the central research tool that compounds across all deliverables.

A specification discovery plugin for Cowork and Claude Code. Helps product managers, founders, and tech leads figure out what to build before writing a single line of code. Unlike tools that assume you already know what to build, ido4shape starts at "tell me about your problem" and guides you through creative, non-linear conversation — reading your documents, asking the questions that matter, surfacing risks you hadn't considered, and tracking understanding across multiple sessions via a persistent knowledge canvas. When understanding is deep enough, it synthesizes a structured strategic specification with capability groups, dependencies, priorities, risk assessments, and verifiable success conditions. Independent parallel reviewers (technical feasibility, scope alignment, dependency audit, format quality) catch issues before the spec is finalized. The output is a standalone markdown document you can hand to your team, feed to any AI coding tool, or use as a project brief. For teams using ido4 MCP, the strate