icaire-roadmap-tasks
Suggest and create ICAIRE roadmap tasks from remote brain progress, member responsibilities, blockers, and open questions. Use when the user asks what tasks should be added next, wants a roadmap-to-ta
SKILL.mdskills/icaire-roadmap-tasks/SKILL.md
GitHubICAIRE Roadmap Tasks
Use the remote ICAIRE brain to turn current progress and gaps into assignable task pages.
Contract
- Use ICAIRE Cortex MCP for all current context.
- Prefer direct task creation when a recommendation is concrete, useful, and assignable to an active member.
- Use
me,members/list,tasks/list,tasks/create, andtasks/updatewhen available; use underscore aliases only if slash tool names fail. - Before creating or updating task pages, call ICAIRE MCP
filing_rulesand follow the compiledFILING.mdguidance it returns. If that tool is unavailable, list and read the relevantFILING.mdfiles directly; do not expect a page namedfiling_rulesto exist. - Do not assign work to arbitrary
people/*pages. Assignees must be active members. - Keep roadmap reasoning grounded in retrieved ICAIRE pages.
- Before marking any task
doneorarchived, either create or link the successor task and useNext task: tasks/<slug>in the timeline entry, or stateNo successor task needed: <reason>.
Workflow
- Call
meandmembers/listto identify the requester and active members. - Retrieve current context:
filing_rulesfor current task-page and routing conventionstasks/listfor existing open, waiting, and blocked tasksqueryorsearchfor initiatives, ops roadmaps, blockers, recent meetings, and inbox questions- direct
readon the most relevant pages
- Identify task candidates:
- overdue or blocked follow-ups
- unowned open questions that should become work
- initiative next steps that are concrete enough to assign
- dependencies or risks that need active resolution
- Deduplicate against existing task pages.
- Create task pages with
tasks/createwhen each task has:- a clear title
- status, priority, and source links
- one or more active member assignees
- a body that explains why the task exists and what good completion means
- When closing an existing task, create or identify the next concrete task
first unless no successor is needed, then include the completion handoff in
tasks/update. - Leave non-actionable or unassignable ideas as recommendations only.
- Verify created tasks with
tasks/listor directread.
Output
Return:
Created Tasks: task slugs, assignees, priority, and sourceSuggested But Not Created: reason each item was not createdExisting Tasks Considered: relevant duplicates or blockersVerification: checks performed
Guardrails
- Do not create speculative tasks that are not grounded in the brain.
- Do not rewrite roadmap or initiative pages unless the user explicitly asks.
- Do not hide missing ownership; report it.
- Do not assign everything to
meunless the brain or user context supports it. - Do not bypass the MCP
filing_rulestool by guessing from stale local conventions or by reading a nonexistentfiling_rulespage.