grinrus/idea-new
skills/idea-new/SKILL.md
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. Do not use when the request is to refresh research artifacts (`researcher`) or draft implementation plans (`plan-new`).
$ install --global
skillsauthnpx skillsauth add grinrus/ai_driven_dev idea-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 9:15 PM181.9s1 file scanned
SKILL.md
- 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. Do not use when the request is to refresh research artifacts (`researcher`) or draft implementation plans (`plan-new`).
- argument-hint:
- $1 [note...]
- lang:
- en
- prompt_version:
- 1.3.23
- source_version:
- 1.3.23
- model:
- inherit
- disable-model-invocation:
- true
- user-invocable:
- true
Follow feature-dev-aidd:aidd-core.
Steps
- Inputs: resolve
<ticket>, parseidea_notefrom user text, and verify PRD/context artifacts are readable for idea stage. - 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 internalslug_hint; ifidea_noteis empty, fallback to<ticket>token. Do not ask user forslug_hint. - Preflight: set active stage
ideaand active feature withpython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.pyandpython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py <ticket> --slug-note "<generated-slug>". - Orchestration: build/update the rolling context pack
aidd/reports/context/<ticket>.pack.mdand runpython3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py --ticket <ticket>. - Run subagent
feature-dev-aidd:analyst. First action: read the rolling context pack. For the persisted PRD artifact, override the global interactive question wording and copy the analyst-dialog labels fromtemplates/prd.template.mdverbatim. - Postflight: reject comment-only placeholders as invalid analyst output. Read-time compatibility still accepts transitional
Question / Why / Options / Default, but the canonical persisted PRD write format remains the template-native Russian wording. - Postflight: if answers already exist, rerun
python3 ${CLAUDE_PLUGIN_ROOT}/skills/idea-new/runtime/analyst_check.py --ticket <ticket>; the validator syncs derived index/status state from the current PRD before returning. - Ready path: return
/feature-dev-aidd:researcher <ticket>only whenanalyst_check.pyconfirms idea-stage readiness. - Pending path: if required questions remain or PRD fields are incomplete, return PENDING with the full current remaining-question set in the top-level response and keep the next action on
idea-new.
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 fromidea_note. - Outputs: updated
aidd/docs/.active.json(ticket+ internalslug_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
- Interactive chat questions still follow the shared aidd-policy format.
- Persisted PRD artifact language is stage-local here: the analyst dialog must use the exact labels from
templates/prd.template.md, and placeholder comments do not count as a valid question block. - Non-interactive callers must rely on the latest top-level stage-return as the source of truth for retry payloads; do not rely only on
AskUserQuestionpanel state or stale example payloads. - 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).
Related Skills
grinrus/tasks-new
tools
VerifiedTrustedCommunity
Derives or refines tasklist items from PRD and plan artifacts. Use when tasklist stage prepares implementation-ready work items. Do not use when the request is plan authoring in `plan-new` or loop execution in `implement`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/status
testing
VerifiedTrustedCommunity
Generates consolidated ticket status summary and key artifact pointers. Use when checking current stage state or handoff readiness. Do not use when the request is diagnostics/inventory from `aidd-observability` or flow-state mutation via `aidd-flow-state`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/spec-interview
testing
VerifiedTrustedCommunity
Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. Do not use when the request is readiness gating in `review-spec` or task derivation in `tasks-new`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/review
testing
VerifiedTrustedCommunity
Runs review-stage validation for scope changes, findings, and follow-up task derivation. Use when review stage needs verdict and handoff tasks. Do not use when the request is direct implementation execution in `implement` or QA validation in `qa`.
5SKILL.mdUpdated Apr 5, 2026