agentsclimarketplace

Cai add roadmap

Skill workingdanny911/dannys-claude/plugins/cai/skills/cai-add-roadmap

Use when recording a future plan or direction. Triggers: 'cai-add-roadmap', 'roadmap 추가', '계획 기록', 'add roadmap', '로드맵 추가', '미래 계획'From its SKILL.md

Install
npx -y skills add workingdanny911/dannys-claude --skill cai-add-roadmap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, as published. Nobody here has run it

CAI Add Roadmap

Overview

Creates a roadmap entry documenting a future plan, direction, or initiative. Uses the cai:cai-interview skill to collect details since future plans cannot be inferred from code.

When to Use

  • AI discovers a future plan during conversation (action routing: "새 roadmap 항목 발견")
  • User mentions upcoming work, migrations, or strategic direction
  • During onboarding Phase 3, user describes future plans

Workflow

1. Determine Status

Ask or infer the roadmap item's current status:

StatusMeaning
exploringUnder consideration, not committed
plannedCommitted but not started
in-progressActive work underway

Note: completed status exists but is set by updating existing items, not by creating new ones.

2. Collect Content

Is there sufficient context in the current conversation?
├── YES → Use it directly (Step 3)
└── NO  → Invoke the cai:cai-interview skill (Step 2a)

2a. Interview for Roadmap Content

Invoke the cai:cai-interview skill. Pass:

  • Goal: Collect the details needed to write a roadmap entry.
  • What is already known: Anything mentioned earlier in the conversation.
  • Output target: This skill's working memory — answers feed Step 3.
  • Seed questions:
    • What is being planned?
    • Why is this needed? (motivation, business driver)
    • Target timeline? (optional)
    • Which existing modules/specs are affected?
    • Known risks or dependencies?

3. Auto-Link Related Specs

Scan context/specs/ to find specs related to the roadmap item:

  • Match by module names mentioned in the plan
  • Match by tags
  • Match by covers paths if the plan mentions specific file areas

Populate the related_specs frontmatter field with paths to matching specs.

4. Write Roadmap Document

Create context/roadmap/{status}/{slug}.md:

---
type: roadmap
status: {exploring|planned|in-progress}
tags: [relevant, tags]
last_synced: {today, YYYY-MM-DD}
target: "{target, e.g., 2026-Q3}"
related_specs: [context/specs/auth/_overview.md]
---
# {Roadmap Item Title}

## Motivation

{Why this is needed, business context}

## Description

{What will be done, scope of the initiative}

## Affected Areas

{Modules, components, or systems that will be impacted}

## Risks & Dependencies

{Known risks, blockers, or dependencies}

The {slug} is derived from the title: lowercase, words joined by hyphens (e.g., "migrate-to-oauth2", "add-real-time-notifications").

5. Confirm with User

Present the generated roadmap item for review. Write to disk only after approval.

Skill Invocations

  • Skill: cai:cai-interview — Collects roadmap details from the user (see Step 2a).

Output

ArtifactPathFormat
Roadmap documentcontext/roadmap/{status}/{slug}.mdMarkdown with YAML frontmatter (Interface Contract 0.1, roadmap type)

Error Handling

ErrorAction
context/roadmap/{status}/ directory does not existCreate it before writing
No related specs foundSet related_specs: [], note this in the document
User provides only a vague ideaSet status to exploring and keep the description high-level
Duplicate roadmap item detected (similar slug exists)Ask user: update existing or create separate item

Keep looking

Skills are one crate of 609,856. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.