icaire-cto-plan-feature-roadmap
Turn ICAIRE product or platform ideas into practical delivery roadmaps. Use when planning feature lists, phases, dependencies, technical risks, staffing needs, or launch criteria.
SKILL.mdskills/icaire-cto-plan-feature-roadmap/SKILL.md
GitHubICAIRE CTO: Plan Feature Roadmap
Use this skill to turn an ICAIRE product, platform, or internal tooling idea into a delivery roadmap that technical and programme teams can execute.
Contract
- Start from the product goal, intended users, operational context, and target delivery horizon.
- Use BigBrain or the ICAIRE MCP connector for ICAIRE initiatives, stakeholders, prior decisions, platform context, and dependencies when the user has not supplied enough source material.
- Separate product outcomes from implementation tasks, technical assumptions, unresolved dependencies, and staffing needs.
- Make sequencing explicit: what must happen first, what can happen in parallel, and what should wait for validation.
- Define launch criteria that cover functionality, security, data handling, reliability, stakeholder acceptance, and operational readiness.
Workflow
- Identify the product or platform idea, target users, use context, deadline, and decision the roadmap needs to support.
- Gather user-provided material and retrieve current ICAIRE context if related initiatives, systems, stakeholders, or constraints are unclear.
- Translate the idea into a concise product objective, user outcomes, and feature set.
- Group features into delivery phases such as discovery, MVP, pilot, launch, and post-launch improvement, unless the user provides another structure.
- For each phase, identify dependencies, technical risks, data or integration needs, staffing needs, review points, and decision gates.
- Define launch criteria and measurable readiness checks.
- List missing information, assumptions, and recommended next actions.
Guardrails
- Do not invent system capabilities, available staff, budgets, partner commitments, launch dates, or approvals.
- Do not over-specify implementation details before user needs and constraints are clear.
- Do not ignore security, privacy, hosting, procurement, or operational support when they affect delivery.
- Do not present aspirational features as committed scope.
- Do not update durable memory unless the user explicitly asks for ingestion or persistence.
Output Expectations
Return a practical roadmap. When useful, include:
- product objective and target users
- feature list
- phased roadmap
- dependencies and prerequisites
- technical risks and mitigations
- staffing or ownership needs
- data, integration, hosting, and security considerations
- launch criteria
- next actions
- missing information or assumptions