Ticket Product Design

JetBrains/thinkrail/claude-plugin/skills/ticket-product-design

creativityOfficial

Official Provider SkillView repo

Produce the product-design.md artifact for a ticket. Asks product clarifying questions (purpose, user stories, value, product/feature success criteria, user scenarios, essence and product outcomes of the feature, feature delivery), presents the design section by section, writes the file, and updates the ticket body with a brief blurb. Use when a ticket is in the `idea` state.

Files1 files

SKILL.md1 lines

Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select AI agent

Select an AI agent above to see the install command.

Manual Install

More steps

Download the file and paste it into your agent's system prompt.

Skill details

Versionv1.0.0

AuthorJetBrains

Categorycreativity

Skill IDJetBrains/thinkrail/claude-plugin/skills/ticket-product-design

Related skills

Architecture DesignCreate a system-wide architecture design document. Use when the user wants to document the overall system architecture, data flow, and design decisions for their project.Bug FixReactive, symptom-driven skill for bug fixes. Edits the project's thinkrail specs to capture the correct intent (or bootstraps a properly-connected spec when the area was uncovered), then suggests a follow-up session to align code to the corrected spec. Treats a bug as a spec/code discrepancy: fix the spec half here; code half is handed off.Cli ProgressShow and track specification-driven development progress. Displays phase progress, milestone completion, and workflow status using thinkrail_visualize. Use at the beginning of any phase or to check overall progress.Goal And RequirementsDefine goal and requirements for a feature, improvement, or change in an existing project. Analyzes the existing codebase first, then helps scope and document what needs to be built. Use when code already exists.Investigate ProjectRead an existing codebase and produce a technical DESIGN_DOC.md plus a draft GOAL&REQUIREMENTS.md from what the code reveals. Use for the existing-project onboarding flow when the user has code but no specs yet.Module DesignCreate a detailed module-level design specification (README.md for a major component). Use when the user wants to document a specific module's architecture, interfaces, and design.