A
AgentSkill
SkillsAbout
A

AgentSkill

ยฉ 2025

Not affiliated with Anthropic

Back to Skills

Code

29 production-ready Claude Code skills for complete Agile workflow automation with Linear integration. From documentation to execution: Epic/Story/Task management, Risk-Based Testing, ADRs, and qualit

Testing
levnikolaevich
11
1
Updated Dec 12, 2025
agile-workflowsarchitecture-decision-recordsclaude-aiclaude-codeclaude-code-pluginclaude-code-skillsdeveloper-toolskanban-boardlinear-integrationproject-managementrisk-based-testingtasks-managerworkflow-automation
View on GitHub

Installation

git clone https://github.com/levnikolaevich/claude-code-skills ~/.claude/skills/code

SKILL.md

# ๐Ÿ‘‹ 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.

![Version](https://img.shields.io/badge/version-10.1.0-blue) ![Skills](https://img.shields.io/badge/skills-29-green) ![Updated](https://img.shields.io/badge/updated-Nov%202025-orange) ![License](https://img.shields.io/badge/license-MIT-green) [![GitHub stars](https://img.shields.io/github/stars/levnikolaevich/claude-code-skills?style=social)](https://github.com/levnikolaevich/claude-code-skills)

---

## ๐Ÿ“– About

This repository contains **29 production-ready skills** for [Claude Code](https://claude.ai/code) that automate and streamline your entire software development lifecycle. From initial documentation to 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

### 1. Documentation System (11X, 12X)

**ln-110-documents-pipeline** orchestrator manages complete documentation lifecycle with idempotent CREATE workflow and global cleanup (Phase 4).

**Orchestrators:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-110-documents-pipeline](ln-110-documents-pipeline/)** | **CREATE Orchestrator** that creates complete documentation system in one command. Sequentially invokes 6 workers: ln-111 (root) โ†’ ln-112 (reference) โ†’ ln-113 (tasks) โ†’ ln-114 (project) โ†’ ln-115 (presentation) โ†’ ln-116 (test, optional). Each worker validates own output (Phase 2/3). **Phase 4**: Global cleanup (deduplication, orphaned files, consolidation, cross-links). **Idempotent**: Pre-flight check shows existing/missing files. | 6.0.0 | โœ… |

**Workers (CREATE path - ln-110):**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-111-root-docs-creator](ln-111-root-docs-creator/)** | Create root documentation entry points: CLAUDE.md + docs/README.md (root hub with general standards) + documentation_standards.md (60 universal requirements). First worker in CREATE path. **Idempotent**: Preserves existing files. | 9.0.0 | โœ… |
| **[ln-112-reference-docs-creator](ln-112-reference-docs-creator/)** | Create reference documentation structure: docs/reference/README.md + adrs/, guides/, manuals/ directories. Second worker in CREATE path. **Idempotent**: Checks 4 items. | 6.0.0 | โœ… |
| **[ln-113-tasks-docs-creator](ln-113-tasks-docs-creator/)** | Create task management documentation: docs/tasks/README.md (task system rules) + kanban_board.md (Linear integration). Third worker in CREATE path. **Idempotent**: Critical kanban_board.md protection. | 6.0.0 | โœ… |
| **[ln-114-project-docs-creator](ln-114-project-docs-creator/)** | Create project documentation BEFORE development: requirements.md, architecture.md, tech_stack.md + 4 optional documents (api_spec, database_schema, design_guidelines, runbook). Fourth worker in CREATE path. **Idempotent**: Tracks created files, edits only new ones. | 11.0.0 | โœ… |
| **[ln-115-presentation-creator](ln-115-presentation-creator/)** | Build interactive HTML presentation from project documentation with 6 tabs (Overview, Requirements+ADRs, Architecture, Technical Spec, Roadmap, Guides). Fifth worker in CREATE path. **Idempotent**: User confirmation for rebuild. | 6.0.0 | โœ… |
| **[ln-116-test-docs-creator](ln-116-test-docs-creator/)** | Create test documentation: testing-strategy.md (universal testing philosophy) + tests/README.md (organization with Story-Level Pattern). Optional sixth worker in CREATE path. **Idempotent**: Checks 4 items. | 6.0.0 | โœ… |

---

### 2. Planning (200-range)

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-221-standards-researcher**).

**Orchestrator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-200-scope-decomposer](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). | 2.0.0 | โœ… |

**Coordinators:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-210-epic-coordinator](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. | 5.0.0 | โœ… |
| **[ln-220-story-coordinator](ln-220-story-coordinator/)** | **Orchestrator** for Story operations. Context Assembly (Phase 1: Epic extraction, frontend research, fallback search) โ†’ Standards Research (Phase 2: delegates **ln-221-standards-researcher**) โ†’ IDEAL Planning (Phase 3: 5-10 Stories, INVEST validation) โ†’ Mode Determination (Phase 4: count existing) โ†’ Delegates CREATE (**ln-222-story-creator**) or REPLAN (**ln-223-story-replanner**). Token efficiency: metadata-only loading (ID/title/status ~50 tokens/Story), workers load full descriptions (~5,000 tokens) when needed. | 4.0.0 | โœ… |

**Worker (Standards Research - ln-220):**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-221-standards-researcher](ln-221-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-310. Time-boxed: 15-20 minutes. | 2.0.0 | โœ… |

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

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-222-story-creator](ln-222-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. | 1.0.0 | โœ… |
| **[ln-223-story-replanner](ln-223-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. | 1.0.0 | โœ… |

---

### 3. Story Pipeline (00, 10-50, 1X-5X)

**Top Orchestrator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-300-story-pipeline](ln-300-story-pipeline/)** | ๐Ÿ”„ **Top orchestrator** for complete Story processing workflow from task planning to Done. Delegates to ln-310-story-decomposer (Phase 2), ln-320-story-validator (Phase 3 Step 1), ln-330-story-executor (Phase 3 Step 2 with To Review โ†’ To Rework โ†’ Todo priorities) and explicitly drives ln-340-story-quality-gate Pass 1 + Pass 2. Looping workflow until Story status = Done. Full pipeline automation: Todo โ†’ In Progress โ†’ To Review โ†’ Done. | 2.0.0 | โœ… |

#### 3.1 Task Planning (ln-310-story-decomposer)

**Coordinator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-310-story-decomposer](ln-310-story-decomposer/)** | **Coordinator** for task operations. Analyzes Story, builds optimal task plan (1-6 tasks, Foundation-First execution order), delegates to ln-311-task-creator (CREATE) or ln-312-task-replanner (REPLAN) with `taskType: "implementation"`. Auto-discovers team ID. For implementation tasks only. | 7.2.0 | โœ… |

**Workers:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-311-task-creator](ln-311-task-creator/)** | **Universal factory** for creating ALL 3 task types (implementation, refactoring, test). Generates task documents from templates, validates type-specific rules, creates in Linear. Invoked by orchestrators (ln-310-story-decomposer, ln-340-story-quality-gate, ln-350-story-test-planner). Owns all 3 templates. | 4.0.0 | โœ… |
| **[ln-312-task-replanner](ln-312-task-replanner/)** | **Universal replanner** for updating ALL 3 task types (implementation, refactoring, test). Compares IDEAL plan vs existing, categorizes operations (KEEP/UPDATE/OBSOLETE/CREATE), applies type-specific validation, executes changes in Linear. Reads templates from ln-311-task-creator/references/. | 4.0.0 | โœ… |

#### 3.2 Story Validation (ln-320-story-validator)

**Coordinator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-320-story-validator](ln-320-story-validator/)** | **Coordinator** that critically reviews Stories and Tasks against 2025 industry standards before approval (Backlog โ†’ Todo). ALWAYS auto-fixes all 16 verification criteria. Auto-creates guides/manuals/ADRs via AUTO-RESEARCH. No "Needs Work" path exists. | 11.0.0 | โœ… |

**Workers:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-321-best-practices-researcher](ln-321-best-practices-researcher/)** | Research best practices via MCP Ref/Context7 and create documentation (guide/manual/ADR). Single research, multiple output types. Replaces ln-321/322/323. | 1.0.0 | โŒ |

#### 3.3 Story Execution (ln-330-story-executor)

**Coordinator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-330-story-executor](ln-330-story-executor/)** | **Coordinator** that orchestrates Story execution (Todo โ†’ In Progress โ†’ To Review โ†’ Done). **Priority 0: Backlog** (auto-verify new tasks before execution) โ†’ **Priority 1: To Review** โ†’ **Priority 2: To Rework** โ†’ **Priority 3: Todo**. Auto-invokes ln-340-story-quality-gate Pass 1 + Pass 2 (full automation). Phase 4 delegates Story quality to ln-340-story-quality-gate (Orchestrator-Worker Pattern). | 7.0.0 | โœ… |

**Workers:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-331-task-executor](ln-331-task-executor/)** | โš™๏ธ Execute implementation tasks ONLY (Todo โ†’ In Progress โ†’ To Review). Uses KISS/YAGNI principles, reads guide links, runs type checking and linting. Story status management removed (now ln-330-story-executor's responsibility). NOT for test tasks. | 10.1.0 | โœ… |
| **[ln-332-task-reviewer](ln-332-task-reviewer/)** | ๐Ÿ” Review completed tasks for To Review โ†’ Done/Rework transition. Distinguishes test/implementation tasks. Checks architecture, docs, security, quality, and test coverage. | 7.3.0 | โœ… |
| **[ln-333-task-rework](ln-333-task-rework/)** | Fix tasks marked To Rework. Analyzes feedback, applies fixes following KISS/YAGNI/DRY principles, runs quality gates (type checking, linting), and submits back To Review. | 5.1.0 | โœ… |
| **[ln-334-test-executor](ln-334-test-executor/)** | โš™๏ธ Execute Story Finalizer test tasks (Todo โ†’ In Progress โ†’ To Review). E2E-first Risk-Based Testing (2-5 E2E, 3-8 Integration, 5-15 Unit). Includes test fixes, infrastructure, docs, and legacy cleanup. | 3.0.0 | โœ… |

#### 3.4 Story Quality Gate (ln-340-story-quality-gate)

**Coordinator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-340-story-quality-gate](ln-340-story-quality-gate/)** | **Coordinator** for Story quality. Pass 1 delegates code analysis to `ln-341-code-quality-checker`, regression to `ln-342-regression-checker`, manual AC verification to `ln-343-manual-tester` (Format v1.0) with FAIL-FAST exit at each gate; auto-creates refactor/bug tasks when any gate fails. When all gates pass, automatically runs `ln-350-story-test-planner` (`autoApprove: true`) to create Story Finalizer test task. Pass 2 verifies automated tests (Priority >=15, limits 10-28) and moves Story to Done. | 7.1.0 | โœ… |

**Workers:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-341-code-quality-checker](ln-341-code-quality-checker/)** | ๐Ÿ”Ž Analyze code quality for DRY/KISS/YAGNI/Architecture violations and guide compliance. Checks git diffs of Done implementation tasks. Reports structured issues by severity (HIGH/MEDIUM/LOW). Fail Fast principle - runs FIRST in Phase 4. | 2.0.0 | โœ… |
| **[ln-342-regression-checker](ln-342-regression-checker/)** | ๐Ÿงช Run existing test suite to verify no regressions. Auto-detects framework (pytest/jest/vitest/go test). Returns JSON verdict + Linear comment. Atomic worker - does NOT create tasks or change statuses. | 1.0.0 | โœ… |
| **[ln-343-manual-tester](ln-343-manual-tester/)** | ๐ŸŽฏ Perform manual functional testing of Story AC using curl (API) or puppeteer (UI). Tests main scenarios + edge cases + error handling + integration. Creates reusable temp script `scripts/tmp_[story_id].sh`. Documents results in Linear (Format v1.0). | 2.0.0 | โœ… |

#### 3.5 Test Planning (ln-350-story-test-planner)

**Coordinator:**

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-350-story-test-planner](ln-350-story-test-planner/)** | **Coordinator** that creates test task for Story after manual testing passes. Analyzes Story, generates comprehensive test task with 11 sections. **Delegates to ln-311-task-creator (CREATE) or ln-312-task-replanner (REPLAN)** with `taskType: "test"`. Supports existing test task updates. Uses 1X workers for task creation/replanning. | 7.2.0 | โœ… |

#### 3.6 Codebase Audit (ln-360-codebase-auditor)

| Skill | Purpose | Version | Diagrams |
|:------|:--------|:-------:|:--------:|
| **[ln-360-codebase-auditor](ln-360-codebase-auditor/)** | Full codebase quality audit across 9 categories (Security, Build, Architecture, Design, Complexity, Algorithms, Dependencies, Wheel Reinvention, Unused Code). Creates consolidated refactoring task in Linear Epic 0. Manual invocation for technical debt assessment. | 1.0.0 | โœ… |

---

## ๐Ÿ“ฅ Installation

### Choose Your Plugin

Select the plugin that matches your team's needs:

| Plugin | Skills | Use Case | Dependencies |
|--------|--------|----------|--------------|
| **complete** โญ | 33 | Full workflow automation (docs + planning + execution) | Linear + Context7 + Ref |
| **docs** | 10 | Documentation automation only | None (standalone) |
| **planning** | 4 | Epic/Story decomposition | Linear + Context7 + Ref |
| **execution** | 19 | Story execution pipeline | Linear + Context7 + Ref |

---

### Installation Methods

**Prerequisites:** [Claude Code CLI](https://claude.ai/code) installed

Choose your installation method:

**Method 1: Plugin Marketplace (Recommended)**
```bash
/plugin marketplace add levnikolaevich/claude-code-skills

# Install complete plugin (recommended for most teams)
/plugin install agile-linear-workflow-complete@agile-linear-workflow-marketplace

# Or install specific plugin
/plugin install agile-linear-workflow-docs@agile-linear-workflow-marketplace
/plugin install agile-linear-workflow-planning@agile-linear-workflow-marketplace
/plugin install agile-linear-workflow-execution@agile-linear-workflow-marketplace

# Verify installation
/skills
```

**Method 2: Direct Plugin**
```bash
/plugin add levnikolaevich/claude-code-skills
/skills  # Verify installation
```

**Method 3: Git Clone**
```bash
# macOS/Linux
git clone https://github.com/levnikolaevich/claude-code-skills.git ~/.claude/skills

# Windows
git clone https://github.com/levnikolaevich/claude-code-skills.git %USERPROFILE%\.claude\skills

# Verify
/skills
```

> ๐Ÿ“– For detailed setup, updates, and configuration, see [Advanced Setup](#-advanced-setup) section below.

---

## ๐Ÿ“Š Visual Documentation

Every skill includes workflow diagrams (`diagram.html`) that visualize execution flow, decision points, and state transitions. Diagrams use Mermaid format and work locally without any server setup.

---

## ๐Ÿ’ก Usage

### Quick Start Example

**Creating Project Documentation:**
```bash
# In Claude Code, invoke the skill
ln-114-project-docs-creator
# Follow the interactive prompts to generate comprehensive documentation
```

**Decomposing Epic into Stories:**
```bash
# Invoke story coordinator with Epic number
ln-220-story-coordinator
# Skill will analyze Epic and create/replan Stories automatically
```

**Executing a Story:**
```bash
# Invoke story executor with Story ID
ln-330-story-executor
# Skill will orchestrate task execution, reviews, and rework
```

### Typical Workflow

**Automated Workflow:**
```
1. ln-110-documents-pipeline โ†’ Create project documentation
2. ln-210-epic-coordinator   โ†’ Decompose scope into Epics
3. ln-220-story-coordinator  โ†’ Create Stories for an Epic (with library research)
4. ln-300-story-pipeline     โ†’ Complete automation from task planning to Done
   โ””โ”€ Orchestrates: task decomposition โ†’ validation โ†’ execution โ†’ quality gates
```

**For manual step-by-step workflow and detailed usage, see [CLAUDE.md](CLAUDE.md).**

---

## ๐Ÿ”ง Advanced Setup

### Prerequisites

Before installation, ensure you have:

- **Claude Code CLI** - Install from [claude.ai/code](https://claude.ai/code)
- **Git** - Required for Method 3 (Git Clone) installation
- **Linear Account** (optional) - For task management integration features
  - Create API key at [linear.app/settings/api](https://linear.app/settings/api)
  - Configure team ID in `docs/tasks/kanban_board.md` (auto-generated by ln-113-tasks-docs-creator)

### Updating

**For Plugin installations (Method 1 or 2):**
```bash
/plugin update agile-linear-workflow
```

**For Git Clone installation (Method 3):**
```bash
# Navigate to skills directory
cd ~/.claude/skills                    # macOS/Linux
cd %USERPROFILE%\.claude\skills       # Windows CMD
cd $env:USERPROFILE\.claude\skills    # Windows PowerShell

# Pull latest changes
git pull origin master
```

### Configuration

**Linear Integration (Optional):** Skills auto-discover configuration from `docs/tasks/kanban_board.md` (Team ID, Epic/Story numbers). Run `ln-113-tasks-docs-creator` to generate config file. No setup required - skills work independently.

---

## ๐Ÿค Contributing

**We warmly welcome contributions!** ๐ŸŽ‰

Whether you're fixing bugs, improving documentation, adding features, or creating new skills - your contributions make this project better for everyone.

**How to contribute:**
- Fork โ†’ Create feature branch โ†’ Submit PR
- Bug fixes, documentation improvements, new skills, translations

**See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines.**

---

## ๐Ÿ“š Documentation

### Core Documentation

- **[CLAUDE.md](CLAUDE.md)** - Comprehensive guide with:
  - Repository structure and skill organization
  - Task hierarchy (Epic โ†’ Story โ†’ Task)
  - Development principles (KISS/YAGNI/DRY, Standards First, Risk-Based Testing)
  - Complete workflow documentation for all skills
  - Template references and best practices
  - Linear integration details

### Skill Structure

Each skill follows a unified structure:
```
x-skill-name/
โ”œโ”€โ”€ SKILL.md              # Metadata and full description
โ”œโ”€โ”€ diagram.html          # Standalone HTML with embedded Mermaid diagram
โ””โ”€โ”€ references/           # Templates and guides
    โ”œโ”€โ”€ template.md       # Document templates
    โ””โ”€โ”€ guide.md          # Reference guides

shared/
โ””โ”€โ”€ css/
    โ””โ”€โ”€ diagram.css       # Universal CSS for all diagrams
```

### Template Ownership Principle

- Each skill owns its templates in its own `references/` directory (Single Source of Truth)
- Templates are NOT copied to project during setup
- Skills use templates directly from their `references/` when generating documents
- Example: ln-321-best-practices-researcher uses `ln-321-best-practices-researcher/references/adr_template.md` when creating ADRs

---

## ๐ŸŒŸ Key Concepts

### Task Hierarchy
```
Epic (Linear Project)
  โ””โ”€โ”€ User Story (Linear Issue with label "user-story")
      โ””โ”€โ”€ Task (Linear Issue with parentId=Story ID)
          โ””โ”€โ”€ Subtask (implementation steps)
```

### Development Principles

**Hierarchy of Principles (when conflicts arise):**
1. **Industry Standards & RFCs** (OAuth 2.0, REST API design, OpenAPI, protocol standards)
2. **Security Standards** (OWASP Top 10, NIST guidelines)
3. **Development Principles** (KISS/YAGNI/DRY apply WITHIN standard boundaries)

**Core Principles:**
- **Standards First** - Follow industry standards before applying KISS/YAGNI
- **YAGNI** - Do not add functionality ahead of time
- **KISS** - Simplest solution that works (within standard boundaries)
- **DRY** - Do not duplicate code
- **Consumer-First Design** - Design APIs/interfaces from consumer perspective (what they need first)
- **Foundation-First Execution** - Build from foundation up (Database โ†’ Repository โ†’ Service โ†’ API) for testability
- **Task Granularity** - Optimal task size 3-5 hours (max 6 tasks per Story)
- **Value-Based Testing** - Prioritize by business risk (2-5 E2E, 3-8 Integration, 5-15 Unit per Story)
- **No Legacy Code** - Remove backward compatibility shims and deprecated patterns

---

## ๐Ÿ“„ License

This project is licensed under the MIT License - see the repository for details.

Feel free to use, modify, and distribute this software in your projects!

---

## ๐Ÿ™ Acknowledgments

- **Claude Code Team** - For creating an amazing AI-powered development environment
- **Linear Team** - For excellent task management and API
- **Mermaid.js** - For beautiful, git-friendly diagrams
- **Community Contributors** - Thank you for making this project better!

---

## ๐Ÿ‘ค Author

**Lev Nikolaevich**
- GitHub: [@levnikolaevich](https://github.com/levnikolaevich)
- Repository: [claude-code-skills](https://github.com/levnikolaevich/claude-code-skills)

---

## ๐Ÿ“ฌ Questions or Feedback?

- ๐Ÿ’ฌ **Discussions** - Share ideas and ask questions in [GitHub Discussions](https://github.com/levnikolaevich/claude-code-skills/discussions)
- ๐Ÿ› **Issues** - Report bugs or request features via [GitHub Issues](https://github.com/levnikolaevich/claude-code-skills/issues)
- โญ **Star this repo** - If you find it useful!

---

<div align="center">

**Happy Coding! ๐Ÿš€**

*Built with โค๏ธ by the community, for the community*

</div>