Linear Issue Architecture with Claude
Architect scoped Linear issues that prevent rework and scope creep
What You Can Do
This skill helps you structure Linear issues and projects with crystal-clear acceptance criteria, task breakdowns, and scope boundaries. You'll reduce rework by systematically architecting issues upfront, catching scope creep before it starts, and surfacing hidden dependencies that would otherwise derail your sprint. By using Claude to design issues methodically, your team executes faster with fewer clarifications and mid-sprint surprises.
Features
Generate standardized issue templates with acceptance criteria, subtasks, and success metrics for features, bugs, and tech debt
Analyze issue descriptions to flag scope expansion risks and suggest how to split bloated issues into smaller, focused ones
Identify hidden dependencies and integration points between issues before work starts to enable parallel execution
Match issue complexity (story points) to your team's capacity and historical burn-down patterns for realistic sprint planning
Convert vague requirements into verifiable, testable criteria that define when work is genuinely done
Surface hidden risks, assumptions, and unknowns in issue descriptions automatically to prevent surprises mid-sprint
Hierarchical decomposition of epics into correctly-scoped issues with clear boundaries and sequencing
Generate context-rich issue descriptions and transition docs to minimize async communication friction across the team
Example Output
Example 1: Transform a vague request into scoped issues
Input: "Build notifications system"
Output:
- 📌 Issue #1: Basic notification schema & storage
Scope: Backend only
Acceptance Criteria:
✓ Design notifications table (userId, type, timestamp, read_at)
✓ Create Notification model with create/update/delete methods
✓ Write unit tests (80% coverage)
Out of Scope: UI, real-time delivery, email notifications
Story Points: 3 | No dependencies
- 📌 Issue #2: In-app notification UI
Scope: Frontend, read-only display
Acceptance Criteria:
✓ Fetch notifications from /api/notifications endpoint
✓ Render notification list with type-specific icons
✓ Mark as read on click
✓ Mobile responsive (375px+)
Out of Scope: Email/SMS delivery, rich formatting
Story Points: 2 | Depends on Issue #1
- 📌 Issue #3: Real-time notification delivery (WebSocket)
Scope: Backend + WebSocket layer
Acceptance Criteria:
✓ Emit notification events via WebSocket when created
✓ Client receives & displays without page refresh
✓ Handle connection failures gracefully
Out of Scope: Push notifications, notification history
Story Points: 5 | Depends on Issue #1 & #2
Example 2: Scope creep detection
Input: "Implement checkout with payments, currency conversion, fraud detection, and wallet support"
Output:
- ⚠️ SCOPE CREEP ALERT: This issue conflates 5 distinct efforts (14-19 story points total).
Recommended split:
- #101: Checkout UI redesign (2pt) ← START HERE
- #102: Stripe payment integration (5pt) | depends on #101
- #103: Multi-currency support (3pt) | depends on #102
- #104: Fraud detection rules (5pt) | depends on #102
- Backlog: Mobile wallet support → propose for Q3
Critical path: 1→2→3&4 in parallel. Total: 15 days, not 1 week.
Example 3: Dependency graph
Initiative: Auth system redesign
[Auth Core] (3pt) — No dependencies
↓
[User Profile] (2pt) [Email Verify] (2pt) — Parallel
↓ ↓
[2FA Setup] (3pt) ← Requires both
- 🟢 Start now: Auth Core
- 🟡 Unblock in 1 week: Profile + Email (parallel)
- 🔴 Unblock in 2 weeks: 2FA
Timeline: 3 weeks to complete. Risk: Email verification blocks 2FA.
What's Included
- SKILL.md: Full issue architecture workflow with decision trees
- Scope creep detection checklist: Patterns to identify and split bloated issues
- Issue template library: Pre-built templates for features, bugs, tech debt, infrastructure
- Dependency mapping workflow: Identify critical path and parallelizable work
- Story point calibration guide: Align estimates to your team's velocity
- Acceptance criteria patterns: Real, testable criteria templates by issue type
- Risk & assumption identification checklist: Surface unknowns before sprint starts
- Handoff documentation templates: Context-rich issue updates for async teams
Who It's For
- Product managers architecting feature roadmaps and sprint planning
- Engineering leads designing sprint scope and preventing rework
- Tech leads breaking down epics into correctly-scoped tasks
- Scrum/Agile masters establishing consistent issue quality standards
- Startup founders shipping faster with clear architectural decisions
Best For
- Complex feature breakdown before implementation starts
- Sprint planning and balancing team capacity
- Epic decomposition and dependency sequencing
- Identifying hidden integration points early
- Preventing scope creep and mid-sprint rework
- Creating clear handoff docs for async teams
- Calibrating story points to team velocity
You might also like
Convert unstructured requirements documents into well-architected Monday.com boards with proper task hierarchies, dependencies, and tracking fields. You'll get automated board structure generation that maps feature requirements to actionable tasks, sets up workflow automation, and configures custom fields for status tracking, priorities, and team assignments.
by mileniumtick
Transform messy stakeholder requirements into organized, relational Notion databases that scale with your product. You'll generate structured specifications with linked requirements, prioritized backlogs, and interactive roadmaps—all ready to import into Notion. Your team gets a single source of truth for product planning.
by mileniumtick
This skill connects to your Monday.com boards, automatically extracts project data, and transforms it into actionable insights. You can analyze timelines, resource allocation, bottlenecks, and progress—then generate polished reports and visualizations ready to share with stakeholders. It accelerates decision-making by condensing hours of manual data collection into seconds.
by mileniumtick
This skill maps interdependencies across functional teams, surfaces critical blockers before they impact delivery, and creates alignment frameworks that keep stakeholders synchronized. You'll identify which teams depend on each other, what tasks are blocking others, which milestones are at risk, and who needs to be in the room to make decisions.
by mileniumtick
Extract and structure product intelligence from Notion databases, then synthesize it into professional briefs, competitive analyses, roadmaps, and requirement specs. You can consolidate scattered insights from multiple database properties and create actionable intelligence for stakeholder communication. This skill transforms raw product data into executive-ready strategic documents.
by mileniumtick
You can generate clear, comprehensive specifications in Confluence that align stakeholders, define measurable acceptance criteria, and identify risks before engineering begins. The skill creates spec templates, validates requirements for completeness, and flags ambiguous language that leads to rework.
by mileniumtick
You can map component dependencies, identify manufacturing bottlenecks, and resolve hardware-specific blockers that would derail sprint commitments. This skill models lead times, tooling constraints, supply chain risks, and resource conflicts to generate realistic sprint timelines and mitigation plans for physical product development.
by mileniumtick
You can analyze sprawling Confluence documentation, extract core concepts and relationships, and transform them into structured knowledge systems that inform product strategy and align stakeholders. The skill identifies knowledge gaps, surfaces cross-cutting concerns, and generates artifact templates (decision matrices, dependency maps, requirements trackers) ready for immediate use in planning and governance.
by mileniumtick