From rapid
Capture out-of-scope feature ideas as backlog items in .planning/backlog/
npx claudepluginhub pragnition/pragnition-public-plugins --plugin rapidThis skill is limited to using the following tools:
You are the RAPID backlog capture skill. This skill persists out-of-scope feature ideas as individual Markdown files in `.planning/backlog/`. It is a capture-only tool -- no listing, browsing, searching, or management features. Follow these steps IN ORDER.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You are the RAPID backlog capture skill. This skill persists out-of-scope feature ideas as individual Markdown files in .planning/backlog/. It is a capture-only tool -- no listing, browsing, searching, or management features. Follow these steps IN ORDER.
Load environment variables before any CLI calls:
if [ -z "${RAPID_TOOLS:-}" ] && [ -n "${CLAUDE_SKILL_DIR:-}" ] && [ -f "${CLAUDE_SKILL_DIR}/../../.env" ]; then export $(grep -v '^#' "${CLAUDE_SKILL_DIR}/../../.env" | xargs); fi
if [ -z "${RAPID_TOOLS}" ]; then echo "[RAPID ERROR] RAPID_TOOLS is not set. Run /rapid:install or ./setup.sh to configure RAPID."; exit 1; fi
Use this environment preamble in ALL subsequent Bash commands within this skill. Every node "${RAPID_TOOLS}" call must be preceded by the env loading block above in the same Bash invocation.
Display the stage banner:
# (env preamble here)
node "${RAPID_TOOLS}" display banner backlog 2>/dev/null || echo "--- /rapid:backlog ---"
If the display banner command is not registered, the fallback echo is sufficient.
The user invokes this skill in one of three ways:
/rapid:backlog "idea title" "description"/rapid:backlog "idea title"/rapid:backlogIf a title was provided as the first argument, use it directly.
If no title was provided, use AskUserQuestion (freeform):
"What feature idea would you like to capture? Provide a short title."
Record the title for use in subsequent steps.
If a description was provided as the second argument, use it directly.
If no description was provided, use AskUserQuestion (freeform):
"Describe this feature idea in 1-3 sentences. What should it do and why would it be valuable?"
Record the description for use in subsequent steps.
Ensure the backlog directory exists:
mkdir -p .planning/backlog
The filename follows the pattern: {YYYYMMDD-HHmmss}-{slug}.md
Generate the timestamp:
date +%Y%m%d-%H%M%S
Generate the slug from the title:
TITLE="<the title from Step 1>"
SLUG=$(echo "$TITLE" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | sed 's/[^a-z0-9-]//g' | cut -c1-50)
echo "$SLUG"
Combine to produce the full filename:
FILENAME="${TIMESTAMP}-${SLUG}.md"
Example: 20260406-143022-add-priority-field-to-backlog.md
Write the file to .planning/backlog/{FILENAME} using the Write tool. The file format is Markdown with YAML frontmatter:
---
title: "{title}"
created: "{ISO 8601 date, e.g. 2026-04-06}"
---
{description}
The frontmatter contains only title and created fields. No source, no priority, no category. The body contains the freeform description exactly as provided.
Display a confirmation message:
Backlog item captured:
.planning/backlog/{FILENAME}Title: {title} Preview: {first 80 characters of description}...
Do NOT commit the file. Backlog items are committed alongside set work -- they merge with the worktree's changes naturally.
skills/*/SKILL.md.planning/backlog/ directly; audit-version surfaces items during milestone review.