👋 Welcome to Claude Code Skills Repository

A comprehensive collection of skills for Claude Code, providing end-to-end Agile workflow automation integrated with Linear for modern software development teams.

---

📖 About

This repository contains 84 production-ready skills for Claude Code that automate and streamline your entire software development lifecycle. From project bootstrapping to documentation, story execution, and quality assurance, these skills work together to create a complete Agile development workflow.

What You Get:

• 🎯 Complete Agile Workflow - From Epic decomposition to task execution and review
• 📋 Linear Integration - Seamless task management and tracking
• 🔄 Automated Workflows - Intelligent orchestration of development tasks
• 📊 Visual Documentation - Mermaid diagrams for every skill workflow
• 🏗️ Best Practices Built-In - KISS/YAGNI/DRY principles, Risk-Based Testing, Industry Standards compliance

Perfect For:

• Software development teams using Agile methodologies
• Projects integrated with Linear for task management
• Teams seeking to automate repetitive development workflows
• Organizations wanting to standardize their development practices

---

🚀 Features

0. Shared & Research Workers (0XX)

Universal research workers for standards, best practices, and architectural patterns. Used across Planning, Task Management, and Quality workflows.

Skill	Purpose	Version	Diagrams
ln-001-standards-researcher	Research industry standards, RFCs, and architectural patterns via MCP Context7 + MCP Ref. Generates Standards Research (Markdown format) for insertion in Story Technical Notes → Library Research subsection. Reusable worker (called by ln-220 Phase 2). Libraries researched at Task level by ln-300. Time-boxed: 15-20 minutes.	3.0.0	✅
ln-002-best-practices-researcher	Research best practices via MCP Ref/Context7 and create documentation (guide/manual/ADR). Single research, multiple output types. Reusable worker (called by ln-310, ln-620).	3.0.0	✅

---

1. Documentation System (1XX)

ln-100-documents-pipeline (L1 Top Orchestrator) manages complete documentation lifecycle with 3-tier architecture and global cleanup (Phase 4).

L1 Top Orchestrator:

Skill	Purpose	Version	Diagrams
ln-100-documents-pipeline	L1 Top Orchestrator that creates complete documentation system in one command. Invokes L2 coordinator (ln-110) + 4 L2 workers (ln-120-150). Phase 4: Global cleanup (deduplication, orphaned files, consolidation, cross-links). Idempotent: Pre-flight check shows existing/missing files.	3.0.0	✅

L2 Coordinator (Project Documentation):

Skill	Purpose	Version	Diagrams
ln-110-project-docs-coordinator	L2 Coordinator that gathers context ONCE, detects project type (hasBackend, hasFrontend, hasDatabase, hasDocker), delegates to 5 L3 workers. Solves "context loss" problem by passing Context Store explicitly.	3.0.0	✅

L3 Workers (Project Documentation - under ln-110):

Skill	Purpose	Version	Diagrams
ln-111-root-docs-creator	Create 4 root docs: CLAUDE.md, docs/README.md, documentation_standards.md, principles.md. ALWAYS invoked.	3.0.0	✅
ln-112-project-core-creator	Create 3 core project docs: requirements.md, architecture.md, tech_stack.md. ALWAYS invoked. High auto-discovery.	3.0.0	✅
ln-113-backend-docs-creator	Create 2 conditional docs: api_spec.md (if hasBackend), database_schema.md (if hasDatabase).	3.0.0	✅
ln-114-frontend-docs-creator	Create 1 conditional doc: design_guidelines.md (if hasFrontend). WCAG 2.1 compliant.	3.0.0	✅
ln-115-devops-docs-creator	Create 1 conditional doc: runbook.md (if hasDocker). Operations guide.	3.0.0	✅

L2 Workers (Other Documentation):

Skill	Purpose	Version	Diagrams
ln-120-reference-docs-creator	Create reference documentation structure: docs/reference/README.md + adrs/, guides/, manuals/ directories. Idempotent: Checks 4 items.	3.0.0	✅
ln-130-tasks-docs-creator	Create task management documentation: docs/tasks/README.md (task system rules) + kanban_board.md (Linear integration). Idempotent: Critical kanban_board.md protection.	3.0.0	✅
ln-140-test-docs-creator	Create test documentation: testing-strategy.md (universal testing philosophy) + tests/README.md (organization with Story-Level Pattern). Optional. Idempotent: Checks 4 items.	3.0.0	✅
ln-150-presentation-creator	Build interactive HTML presentation from project documentation with 6 tabs (Overview, Requirements+ADRs, Architecture, Technical Spec, Roadmap, Guides). Idempotent: User confirmation for rebuild.	3.0.0	✅

---

2. Planning (2XX)

Orchestrator-Worker Pattern applied to decomposition workflow. ln-200-scope-decomposer (TOP orchestrator) automates full decomposition (scope → Epics → Stories) by delegating to ln-210-epic-coordinator (CREATE/REPLAN Epics) → ln-220-story-coordinator (CREATE/REPLAN Stories with Phase 2 standards research via ln-001-standards-researcher) → ln-230-story-prioritizer (RICE prioritization per Story with market research).

Orchestrator:

Skill	Purpose	Version	Diagrams
ln-200-scope-decomposer	TOP Orchestrator for full decomposition automation (scope → Epics → Stories). Sequentially delegates: ln-210-epic-coordinator (Phase 2) → ln-220-story-coordinator loop per Epic (Phase 3). User confirmation required (Phase 1). Provides summary + next steps (Phase 4).	3.0.0	✅

Coordinators:

Skill	Purpose	Version	Diagrams
ln-210-epic-coordinator	Domain Coordinator that decomposes scope into 3-7 Linear Projects (Epics) with business goals, success criteria, and phased strategy. Decompose-First Pattern: builds IDEAL plan → checks existing → CREATE/REPLAN mode (KEEP/UPDATE/OBSOLETE/CREATE). Auto-discovers team ID.	3.0.0	✅
ln-220-story-coordinator	Coordinator for Story operations. Context Assembly (Phase 1: Epic extraction, frontend research, fallback search) → Standards Research (Phase 2: delegates ln-001-standards-researcher) → IDEAL Planning (Phase 3: 5-10 Stories, INVEST validation) → Mode Determination (Phase 4: count existing) → Delegates CREATE (ln-221-story-creator) or REPLAN (ln-222-story-replanner). Token efficiency: metadata-only loading (ID/title/status ~50 tokens/Story), workers load full descriptions (~5,000 tokens) when needed.	3.0.0	✅

Workers (CREATE/REPLAN path - ln-220):

Skill	Purpose	Version	Diagrams
ln-221-story-creator	Creates Stories from IDEAL plan (ln-220 Phase 5a). Generates 8-section documents with Standards Research insertion (Technical Notes), validates INVEST criteria, shows preview, creates in Linear (project=Epic, labels=user-story, state=Backlog), updates kanban_board.md via Epic Grouping Algorithm. First-time Epic decomposition. Owns story_template_universal.md.	3.0.0	✅
ln-222-story-replanner	Replans Stories when Epic requirements change (ln-220 Phase 5b). Progressive Loading (ONE BY ONE for token efficiency: ~5,000 tokens/Story), compares IDEAL vs existing, categorizes operations (KEEP/UPDATE/OBSOLETE/CREATE), shows diffs (AC, Standards Research, Technical Notes), user confirmation, executes updates (respects status constraints: Backlog/Todo only), updates kanban_board.md. Story Split/Merge detection.	3.0.0	✅

Story Prioritization (after ln-220):

Skill	Purpose	Version	Diagrams
ln-230-story-prioritizer	L2 Worker for Story-level RICE prioritization after ln-220. Loads Stories from Epic, researches market size and competition per Story via WebSearch/Ref, calculates RICE score (Reach × Impact × Confidence / Effort), assigns Priority (P0-P3) with Competition Index (Blue 1-2 / Red 4-5). Generates consolidated table in docs/market/[epic-slug]/prioritization.md. Time-boxed: 40-60 minutes.	3.0.0	✅

---

3. Task Management (3XX)

Task planning and Story validation workflows. ln-300-task-coordinator decomposes Stories into 1-6 implementation tasks. ln-310-story-validator validates Stories/Tasks against 2025 standards (CRITICAL PATH FIRST) with auto-fixes and research via ln-002-best-practices-researcher.

Coordinators:

Skill	Purpose	Version	Diagrams
ln-300-task-coordinator	Coordinator for task operations.