// Create and manage CloudBurn roadmap items. Use this skill whenever the user wants to add a feature request, improvement idea, or any item to the CloudBurn roadmap.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
| name | roadmap |
| description | Create and manage CloudBurn roadmap items. Use this skill whenever the user wants to add a feature request, improvement idea, or any item to the CloudBurn roadmap. |
You help users add items to the CloudBurn Roadmap GitHub Project board. The user describes what they want — you turn it into a well-structured GitHub issue and place it in the Researching column.
Before creating anything, assess whether you have enough context to write a useful issue. You need three things:
If the user gives you enough detail to answer all three confidently, skip straight to Phase 2. Don't interview for the sake of interviewing.
Example: "Add a rule that detects idle RDS instances with zero connections over 14 days" — you know the what, why, and scope. Go create it.
If the request is too vague, use the AskUserQuestion tool to gather what you need. This keeps the conversation structured and gives the user clear options to pick from.
Guidelines:
AskUserQuestion with 1-3 focused questions to fill the gapsExample: if the user says "we should support Azure", use AskUserQuestion with a question like:
After the user responds, you should have enough to proceed. If something is still unclear, one more AskUserQuestion round is fine — but no more than two rounds total. Fill remaining gaps with reasonable assumptions and note them in the issue body.
| Label | Use when... |
|---|---|
enhancement | New feature, capability, rule, or improvement to existing behavior |
bug | Something is broken or behaving incorrectly |
documentation | Docs are missing, unclear, or need updating |
Default to enhancement — most roadmap items are enhancements.
Title: Short, specific, action-oriented. Start with a verb when natural. Keep under 70 characters.
Examples:
Body: Clear, well-structured description. Adapt the structure to what makes sense — not every issue needs every section:
Keep it concise. Don't pad with filler or repeat the title in the body.
Step 1 — Create the GitHub issue:
gh issue create \
--repo towardsthecloud/cloudburn \
--title "<title>" \
--label "<label>" \
--body "$(cat <<'EOF'
<body>
EOF
)"
Capture the issue URL from the output.
Step 2 — Add the issue to the roadmap project:
gh project item-add 4 --owner towardsthecloud --url <issue-url> --format json
Extract the id field from the JSON response.
Step 3 — Set status to "Researching":
gh project item-edit \
--project-id PVT_kwDOC--Ra84BG8XH \
--id <item-id> \
--field-id PVTSSF_lADOC--Ra84BG8XHzg317rI \
--single-select-option-id f75ad846
Step 4 — Confirm to the user with the issue title, label, and link. Keep it brief.
Stable identifiers for the CloudBurn Roadmap project board:
4PVT_kwDOC--Ra84BG8XHtowardsthecloudtowardsthecloud/cloudburnPVTSSF_lADOC--Ra84BG8XHzg317rIf75ad8468185493e47fc9ee498236657