Skills Guide

Bootstrap New Feature Ticket

VerifiedSafe

Bootstraps a new feature ticket by setting active context, deriving a slug hint from the idea note, and preparing PRD questions. Use at the idea stage to initialize the ticket workflow and validate PRD readiness.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#feature-ticket#idea-stage#bootstrapping#prd#project-management

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Bootstraps a new feature ticket by setting the active context, generating an internal slug, and preparing PRD questions for the idea stage.

Strengths

  • Automates slug generation and active context setup.
  • Integrates a validation step (analyst_check) for PRD readiness.
  • Provides clear, repeatable command contracts.
  • Reduces friction when starting a new feature idea.

Limitations

  • Requires a Claude Code environment with specific plugins installed.
  • Only works if the ticket and PRD artifacts are readable.
  • Runs in non-interactive mode (disable-model-invocation), limiting real-time user guidance.
When to use it

Use this skill when you need to kick off a new feature ticket and lay the groundwork for subsequent analysis and research.

When not to use it

Avoid using it if the ticket does not exist yet or if you are not following the feature-dev-aidd workflow.

Security analysis

Safe
Quality score90/100

The skill uses only read, edit, write, glob, and restricted bash (rg, sed) tools, plus specific Python scripts from the plugin. No destructive, exfiltrating, or obfuscated actions. It delegates to a subagent but does not execute arbitrary commands.

No concerns found

How this analysis is made

Examples

Basic feature idea with note
idea-new TICKET-123 This feature should allow users to export reports as PDF with customizable formatting.
Fallback when idea note is empty
idea-new TICKET-456

name: idea-new description: Bootstraps a new feature ticket by setting active context, deriving slug_hint, and preparing PRD questions. Use when the idea stage starts for a new ticket. argument-hint: $1 [note...] lang: ru prompt_version: 1.3.21 source_version: 1.3.21 allowed-tools:

  • Read
  • Edit
  • Write
  • Glob
  • "Bash(rg *)"
  • "Bash(sed *)"
  • "Bash(python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-rlm/runtime/rlm_slice.py *)"
  • "Bash(python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py *)"
  • "Bash(python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.py *)"
  • "Bash(python3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py *)" model: inherit disable-model-invocation: true user-invocable: true

Follow feature-dev-aidd:aidd-core.

Steps

  1. Inputs: resolve <ticket>, parse idea_note from user text, and verify PRD/context artifacts are readable for idea stage.
  2. Slug synthesis: generate a short LLM summary from idea_note, normalize it into kebab-case token ([a-z0-9-], 2-6 words), and use it as internal slug_hint; if idea_note is empty, fallback to <ticket> token. Do not ask user for slug_hint.
  3. Preflight: set active stage idea and active feature with python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.py and python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py <ticket> --slug-note "<generated-slug>".
  4. Orchestration: build/update the rolling context pack aidd/reports/context/<ticket>.pack.md and run python3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py --ticket <ticket>.
  5. Run subagent feature-dev-aidd:analyst. First action: read the rolling context pack.
  6. Postflight: if answers already exist, rerun python3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py --ticket <ticket> and sync PRD readiness status.
  7. Output: return open questions (if any) and explicit next step /feature-dev-aidd:researcher <ticket>.

Command contracts

python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py

  • When to run: once ticket and idea note are parsed, before analyst execution.
  • Inputs: <ticket> and generated --slug-note <slug_hint> derived from idea_note.
  • Outputs: updated aidd/docs/.active.json (ticket + internal slug_hint) and PRD scaffold.
  • Failure mode: non-zero exit when workspace paths/permissions are invalid.
  • Next action: fix workspace issue, keep the same generated slug policy, rerun the command.

python3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py

  • When to run: before/after analyst execution to validate PRD readiness and Q/A synchronization.
  • Inputs: --ticket <ticket> and active workspace artifacts.
  • Outputs: deterministic readiness status for idea-stage gate decisions.
  • Failure mode: non-zero exit when required PRD fields or answer alignment are missing.
  • Next action: update PRD/QA artifacts, then rerun the same validator.

Notes

  • Use the aidd-core question format.
  • Planning stage: AIDD:ACTIONS_LOG: n/a.

Additional resources

  • PRD template source: templates/prd.template.md (when: defining or validating required PRD structure; why: keep analyst output aligned with canonical sections).

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/bootstrap-new-feature-ticket-mm5t8bb1/download' --output '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md.part' && mv '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md.part' '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md' && test -s '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/idea-new' && cp -R '.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1' '.claude/skills/idea-new'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1'

openskills read 'bootstrap-new-feature-ticket-mm5t8bb1'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/bootstrap-new-feature-ticket-mm5t8bb1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot