Jira Natural Language Interface
jjmartres/opencode
Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.
Define or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence.
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Cranot/roam-code roam-milestone-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .claude/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .claude/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Cranot/roam-code roam-milestone-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .agents/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .agents/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Cranot/roam-code roam-milestone-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .cursor/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .cursor/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Cranot/roam-code.git --path .agents/skills/roam-milestone-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Cranot/roam-code roam-milestone-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .gemini/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .gemini/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Cranot/roam-code roam-milestone-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .github/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .github/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Cranot/roam-code --skill roam-milestone-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Cranot/roam-code roam-milestone-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Cranot/roam-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/roam-milestone-planning .opencode/skills/roam-milestone-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "roam-milestone-planning" agent skill from https://github.com/Cranot/roam-code/tree/main/.agents/skills/roam-milestone-planning into .opencode/skills/roam-milestone-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roam-milestone-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
roam-milestone-planningDefine or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence.
Roam Milestone Planning is an agent skill from Cranot/roam-code. Define or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence. Use for a requested goal or priority guide across those areas, not a single implementation task, routine status report, copy edit or publication operation.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management. It works with Model Context Protocol. The repository describes itself as: Local codebase intelligence CLI + MCP server for AI coding agents: SQLite code graph, 28 languages, 287 commands, 246 MCP tools, change-safety gates, audit evidence, zero API keys. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit f0bdb63. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Roam Milestone Planning loads about 1.2k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 621 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Cranot/roam-code at commit f0bdb63, republished under its Apache-2.0 licence (© Cranot). 621 words, ~1,195 tokens.
.claude/skills/roam-milestone-planning/SKILL.md (or your agent's skills folder).Turn ambition into bounded supported outcomes and executable decisions. Preserve Roam's broad free mechanical tools and the consumer's direction, execution authority and acceptance. A milestone is not a new package version or release verdict.
Work in the Roam repository. Read docs/understanding-roam.md, then the relevant
direction in internal/ROAM-NORTH-STAR.md. Consult internal/WORK-GUIDE.md,
internal/INTERNAL-V1.md when applicable, and internal/EXECUTION-SEQUENCE.md
for principles, milestone scope and current action respectively. Open the
selected task cards and source-bound reports, not the entire historical archive.
If private sources are missing, name the gap; a title is not their contents.
Separate an owner's adopted decision from a recommendation, observation or discarded experiment. Reconcile evidence by the actual artifact, environment and reach; recency alone does not supersede a broader valid result. An old document calling itself the live board does not make it the active cursor. Correct conflicting routing without rewriting historical observations. Use a distinct identifier when a new milestone collides with a legacy task or schema.
Qualify recurring tasks and actual consumers, not command counts. Include healthy/no-change work and useful partial results as well as real findings. Name the installed artifact, repository slice, client/preset, intended decision, acceptance consumer and recovery path where they affect the promise. Indexed analysis and fixed execution/replay have different evidence foundations.
For each requirement, distinguish:
Do not average away a required failure or turn every uncertain hypothesis into a launch blocker. A named support slice does not excuse a severe known defect in a shared boundary or an available path with a materially misleading promise. Keep a truthful account of available breadth; do not quietly delete the free catalogue or invent universal compatibility.
Separate engineering readiness, deliverable-offer readiness and actual demand, retention or delivery economics. Paid engagement cannot responsibly precede its required handling/capacity/terms, but a completed sale or retention study cannot be a circular prerequisite for beginning any offering. Internal work can expose a real defect without an external buyer. Keep adopted offer direction; do not invent prices, demand, staffing or a new commercial surface to complete a plan.
Reuse existing cards, their acceptance and the single execution cursor. The milestone document owns scope and exits, not another daily status board. Name dependencies, the smallest useful next output, its acceptance/refuter and what happens if it fails or is unavailable. Do not activate the whole sequence.
Preserve a frozen candidate's identity. New unrelated work gets a separate bounded decision instead of keeping the release open indefinitely. A blocked external step may leave useful authorized local preparation. A narrower release can ship independently only when its own promises and gates genuinely qualify; that does not complete a broader milestone.
Challenge the draft from the actual agent, adopter, maintainer, evidence consumer and buyer viewpoints. Look for omitted work, conflicting promises, circular gates and cheaper discriminating tests. Retain correct decisions; do not manufacture a rewrite, new command or benchmark platform. Record meaningful revisions and the evidence boundary of this review, not a confidence score. Check the work behind the promise as well as its wording: installation, artifact/dependency hygiene, support burden and recovery. Readiness requires the actual relevant path, not another document asserting that it exists.
Before handing off, check source links, owner routing, proposed versus current
state and the next executable action. Keep plans and evaluations in internal/.
A plan authorizes neither publishing nor source transfer, contact, spending or
work in another repository. Surface those choices only when the exact operation
needs them; missing external authority does not prohibit safe local planning.
© Cranot, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/roam-milestone-planning of Cranot/roam-code.
Open the folder on GitHubat commit f0bdb63
Roam Milestone Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Roam Milestone Planning this skillCranot/roam-code | 517 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Jira Natural Language Interfacejjmartres/opencode | 133 | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Fireauto Project Guideimgompanda/fireauto | 140 | — | ~674 | Automated safety check: Pass | MIT | |
| PiyazFrkAk/piyaz | 194 | — | ~13k | Automated safety check: Pass | AGPL-3.0 | |
| Releases-morgan-jeffries/apple-mail-fast-mcp | 104 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Project ManagerTh0rgal/sandboxed.sh | 516 | — | ~1.8k | Automated safety check: Pass | MIT |
jjmartres/opencode
Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.
imgompanda/fireauto
프로젝트 생성, 마일스톤 관리, 태스크 추적이 필요할 때 사용하세요. An agent skill from imgompanda/fireauto.
FrkAk/piyaz
A skill your agent uses when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work…
s-morgan-jeffries/apple-mail-fast-mcp
A skill your agent uses when the user wants to release a new version.
Th0rgal/sandboxed.sh
Steer sandboxed.sh projects, roadmaps, decisions from chat. An agent skill from Th0rgal/sandboxed.sh.
alirezarezvani/claude-skills
A skill your agent uses when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin…
Cranot/roam-code
Codebase comprehension via roam-code CLI. An agent skill from Cranot/roam-code.
Cranot/roam-code
Review and maintain the technical instructions Roam gives coding agents: shipped skills, tool descriptions, preset guidance and generated instruction blocks.
Cranot/roam-code
Investigate and harden Roam detectors, CLI/MCP result contracts, and evidence consumers when dogfooding or correcting incomplete, misleading, or inconsistent analysis.
Cranot/roam-code
Turn a reproduced or recurring Roam failure into a durable correction, regression control or narrowly scoped project skill, and reconcile conflicting lessons.
Cranot/roam-code
Design or interpret a comparison of Roam performance, detector accuracy, retrieval or workflow value.
Cranot/roam-code
Qualify a Roam commit or accumulated batch for package, website, or server publication; reconcile source, tests, review, CI and deployed identities, and identify the next authorized release step.
Works with
Categories
Define or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence. Roam Milestone Planning is an agent skill from Cranot/roam-code. Define or revise a Roam product milestone and its engineering, adoption and offer-readiness sequence.
Roam Milestone Planning fits situations like: A requested goal; priority guide across those areas; not a single implementation task; routine status report.
Run `npx skills add Cranot/roam-code --skill roam-milestone-planning -a claude-code`. Or copy the skill folder (.agents/skills/roam-milestone-planning in Cranot/roam-code) into .claude/skills/roam-milestone-planning in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Cranot/roam-code --skill roam-milestone-planning -a codex`. Or copy the skill folder (.agents/skills/roam-milestone-planning in Cranot/roam-code) into .agents/skills/roam-milestone-planning in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Cranot/roam-code --skill roam-milestone-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/roam-milestone-planning, .gemini/skills/roam-milestone-planning, .github/skills/roam-milestone-planning and .opencode/skills/roam-milestone-planning in your project.
SKILL.md names no scripts, command-line tools or credentials: Roam Milestone Planning is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Roam Milestone Planning is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Roam Milestone Planning: Jira Natural Language Interface (jjmartres/opencode, 133 stars), Fireauto Project Guide (imgompanda/fireauto, 140 stars), Piyaz (FrkAk/piyaz, 194 stars) and Release (s-morgan-jeffries/apple-mail-fast-mcp, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Cranot (a GitHub user) maintains it in Cranot/roam-code, which has 517 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.
Source: Cranot/roam-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.