AgentSkillsCN

linear-project-creation

通过深度访谈与探索，打造并优化Linear项目

SKILL.md
--- frontmatter
name: linear-project-creation
description: Create and refine Linear projects through in-depth interviewing and exploration

Linear Project Creation

Create or refine a Linear project through in-depth interviewing and codebase exploration. This skill requires Linear MCP.

Requirements

  • •Linear MCP must be configured and authenticated
  • •User must have access to create/edit projects in Linear

Process

Step 1: Get or Create Linear Project

Ask the user:

  • •Existing project: Provide the Linear project ID to refine
  • •New project: Provide a name and team, Claude will create it

If creating new:

  1. •Use Linear MCP to create the project
  2. •Return the project ID to the user

If existing:

  1. •Fetch the project via Linear MCP
  2. •Read current description and status

Step 2: Interview & Explore Loop

This step repeats until both Claude and the user are satisfied.

2a: Interview

Interview the user in detail about literally anything relevant to the project:

  • •Technical implementation and architecture
  • •UI/UX considerations
  • •Performance concerns and constraints
  • •Edge cases and failure modes
  • •Tradeoffs and alternatives considered
  • •Dependencies and integration points
  • •Security and reliability requirements

Important guidelines:

  • •Ask questions in batches of 2-3 (less overwhelming)
  • •Make sure questions are not obvious - dig deeper than surface level
  • •Don't ask things you could figure out by reading the code
  • •Challenge assumptions - ask "why" and "what if"
  • •Be in-depth, not superficial

Bad questions (too obvious):

  • •"What problem does this solve?" (ask for the spec first, then go deeper)
  • •"What are the requirements?" (too generic)

Good questions (specific, probing):

  • •"You mentioned X - how should that behave when Y happens?"
  • •"I see the current implementation does Z - are we keeping that pattern or changing it?"
  • •"What's the failure mode if the upstream service is slow?"
  • •"Is there a performance budget for this? Latency constraints?"

2b: Explore

Based on the user's answers, gather relevant context:

Codebase exploration:

  • •Read files in the relevant area of the codebase
  • •Look for existing patterns or similar implementations
  • •Check tests to understand expected behavior
  • •Identify interfaces or contracts that matter

Linear exploration:

  • •Fetch related Linear projects or issues
  • •Check for prior work or dependencies
  • •Look at how similar features were scoped

Summarize findings: After exploring, briefly summarize what you learned and how it informs the spec.

2c: Check Satisfaction

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):

  • •User signals done: "That's enough" / "Looks good" / "Let's write it up"
  • •Claude is confident: "I think I have enough context to write a solid spec - ready to proceed?"

If neither condition is met, loop back to 2a with more targeted questions based on gaps identified.

Step 3: Update Linear Project

After the loop completes, update the Linear project description with:

code
## 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.

Step 4: Confirm

  • •Show the user the updated project description
  • •Provide the Linear project URL
  • •Ask if they want to proceed to creating tickets (linear-project-to-tickets)

Behavior Notes

  • •Always use Linear MCP - no fallback to local markdown
  • •Be thorough but not tedious - know when to stop
  • •Explore proactively - don't wait to be asked
  • •Keep exploration focused - read relevant files, not the entire codebase
  • •Summarize findings concisely before asking for more input
  • •The loop should feel collaborative, not interrogative
  • •Always ask about target release for labeling

Linear Label Structure

Linear uses nested labels for releases. When applying release labels:

  • •Labels are organized in groups (e.g., "Dynamo Releases")
  • •Release labels are children of these groups (e.g., "Dynamo Releases > Dynamo 0.9.0")
  • •When searching for labels via MCP, look for the parent group first, then the specific release
  • •Example: To label for Dynamo 0.9.0, find "Dynamo Releases" group, then select "Dynamo 0.9.0"