Create and refine Linear projects through in-depth interviewing and exploration
Creates and refines Linear projects through in-depth interviews and codebase exploration.
/plugin marketplace add ishandhanani/dynamo-claude-plugin/plugin install ishandhanani-dynamo@ishandhanani/dynamo-claude-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create or refine a Linear project through in-depth interviewing and codebase exploration. This skill requires Linear MCP.
Ask the user:
If creating new:
If existing:
This step repeats until both Claude and the user are satisfied.
Interview the user in detail about literally anything relevant to the project:
Important guidelines:
Bad questions (too obvious):
Good questions (specific, probing):
Based on the user's answers, gather relevant context:
Codebase exploration:
Linear exploration:
Summarize findings: After exploring, briefly summarize what you learned and how it informs the spec.
Ask the user:
"Based on what we've discussed and what I found, do you have more context to add? Or is there anything else I should explore?"
Exit conditions (move to Step 3 when either is met):
If neither condition is met, loop back to 2a with more targeted questions based on gaps identified.
After the loop completes, update the Linear project description with:
## Problem Statement
[1-2 sentences on what problem this solves]
## Goals
- [Concrete, measurable goal]
## Non-Goals
- [Explicitly out of scope]
## Requirements
### Must Have
- [Requirement with acceptance criteria]
### Nice to Have
- [Lower priority]
## Technical Approach
[High-level approach, not implementation details]
## Success Metrics
- [How we measure success]
## Target Release
[Release label, e.g., "Dynamo Releases > Dynamo 0.9.0"]
## Risks & Dependencies
- [Known risks and dependencies]
## Context Gathered
[Brief summary of relevant code, patterns, or related issues discovered during exploration]
Use Linear MCP to update the project description directly.
linear-project-to-tickets)Linear uses nested labels for releases. When applying release labels:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.