[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NHT53DBPSH6WHQ6Y9GSZ3":3,"skill-same:01M71NHT53DBPSH6WHQ6Y9GSZ3":114},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M71NHT53DBPSH6WHQ6Y9GSZ3","ln-130-tasks-docs-creator",null,"Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.","vitalikpestov\u002FSkills-Catalog","vitalikpestov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13882997?v=4","01M71N4QG0CWRXX4R24JQZXDDQ","Vitalik Pestov","01M71N4QGMSYRW607DDSE0CQMM",2,"MIT","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"tasks","creator","ln","docs creator","ln 130 tasks docs creator","docs","task","setting","when","for","sonnet","project","tracker","kanban board","kanban","up","use","Rules","task management","workflow","2026-11-10 10:56:23",false,"---\nname: ln-130-tasks-docs-creator\ndescription: \"Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.\"\nlicense: MIT\nmodel: claude-sonnet-4-6\n---\n\n> **Paths:** File paths (`references\u002F`, `..\u002Fln-*`) are relative to this skill directory.\n\n**Type:** L2 Worker\n**Category:** 1XX Documentation Pipeline\n\n# Tasks Documentation Creator\n\nThis skill creates task management documentation: docs\u002Ftasks\u002FREADME.md (task management system rules) and docs\u002Ftasks\u002Fkanban_board.md (configured tracker integration with Epic Story Counters).\n\n## Purpose\n\nCreate and validate task management documentation (docs\u002Ftasks\u002F). Generates README.md with workflow rules and kanban_board.md with tracker integration that adapts to the configured provider (linear\u002Fgithub\u002Ffile), including interactive setup for provider-specific configuration.\n\n## When to Use This Skill\n\n**This skill is a L2 WORKER** invoked by **ln-100-documents-pipeline** orchestrator OR used standalone.\n\nUse this skill when:\n- Creating task management documentation (docs\u002Ftasks\u002F)\n- Setting up tracker integration and kanban board\n- Validating existing task documentation structure and content\n- Configuring provider-specific tracker settings (linear: Team Name\u002FUUID\u002FKey; github: repository\u002Fproject_number; file: nothing)\n\n**Part of workflow**: ln-100-documents-pipeline → ln-110-project-docs-coordinator → ln-120-reference-docs-creator → **ln-130-tasks-docs-creator** → ln-140-test-docs-creator (optional)\n\n## Workflow\n\nThe skill follows a **3-phase workflow**: CREATE → VALIDATE STRUCTURE → VALIDATE CONTENT.\n\n**MANDATORY READ:** Load `references\u002Fdocs_quality_contract.md`, and `references\u002Fmarkdown_read_protocol.md`.\nOptional rule catalog: load `references\u002Fdocs_quality_rules.json` only when exact rule IDs, path matrices, or allowlisted placeholder exceptions are needed.\n\n**Phase 1: CREATE** - Create tasks\u002FREADME.md from template with SCOPE tags, workflow rules, configured tracker integration\n**Phase 2: VALIDATE STRUCTURE** - Auto-fix structural violations (SCOPE tags, sections, Maintenance, POSIX)\n**Phase 3: VALIDATE CONTENT** - Validate semantic content + provider-conditional Tracker Configuration handling (placeholder detection, provider-specific field validation, interactive user prompts). Raw placeholders are allowed only during setup for `docs\u002Ftasks\u002FREADME.md` and `docs\u002Ftasks\u002Fkanban_board.md`; published output must not leak unresolved markers into any other document.\n\n---\n\n## Phase 1: Create tasks\u002FREADME.md\n\n**Objective**: Create task management system documentation from template.\n\n**When to execute**: Always (first phase)\n\n**Process**:\n\n1. **Check if tasks\u002FREADME.md exists**:\n   - Use Glob tool: `pattern: \"docs\u002Ftasks\u002FREADME.md\"`\n   - If file exists:\n     - Skip creation\n     - Log: `✓ docs\u002Ftasks\u002FREADME.md already exists (preserved)`\n     - Proceed to Phase 2\n   - If NOT exists:\n     - Continue to step 2\n\n2. **Create tasks directory**:\n   - Create the `docs\u002Ftasks\u002F` directory if it doesn't exist\n\n3. **Create tasks\u002FREADME.md from template**:\n   - **MANDATORY READ:** Load `references\u002Ftemplates\u002Ftasks_readme_template.md`\n   - Copy template → `docs\u002Ftasks\u002FREADME.md`\n   - Replace placeholders:\n     - `{{DATE}}` → current date (YYYY-MM-DD)\n   - Template contains:\n     - Full shared header contract (`SCOPE`, `DOC_KIND`, `DOC_ROLE`, `READ_WHEN`, `SKIP_WHEN`, `PRIMARY_SOURCES`)\n     - Story-Level Test Task Pattern\n     - Kanban Board Structure (Epic Grouping Pattern)\n     - Linear Integration (MCP methods)\n     - Quick Navigation, Agent Entry, and Maintenance sections\n\n4. **Notify user**:\n   - If created: `✓ Created docs\u002Ftasks\u002FREADME.md with task management rules`\n   - If skipped: `✓ docs\u002Ftasks\u002FREADME.md already exists (preserved)`\n\n**Output**: docs\u002Ftasks\u002FREADME.md (created or existing)\n\n---\n\n## Phase 2: Validate Structure\n\n**Objective**: Ensure tasks\u002FREADME.md and kanban_board.md comply with structural requirements. Auto-fix violations.\n\n**When to execute**: After Phase 1 completes (files exist or created)\n\n**Process**:\n\n### 2.1 Validate SCOPE tags\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Read the opening block\n2. Check for `\u003C!-- SCOPE: ... -->` tag and metadata markers\n3. Expected values:\n   - tasks\u002FREADME.md: `\u003C!-- SCOPE: Task tracking system workflow and rules ONLY -->`\n   - kanban_board.md: `\u003C!-- SCOPE: Quick navigation to active tasks in Linear -->`\n4. **If missing:**\n   - Use Edit tool to add SCOPE tag after first heading\n   - Log: `⚠ Auto-fixed: Added missing SCOPE tag to {filename}`\n\n### 2.2 Validate required sections\n\n**MANDATORY READ:** Load `references\u002Fquestions.md` for validation specs (section names, heuristics, special handling rules).\n\n**For tasks\u002FREADME.md**:\n- Required sections (from questions.md):\n  - \"Linear Integration\" OR \"Core Concepts\" (Linear MCP methods)\n  - \"Task Workflow\" OR \"Critical Rules\" (state transitions)\n  - \"Task Templates\" (template references)\n- For each section:\n  - Check if section header exists (case-insensitive)\n  - **If missing:**\n    - Use Edit tool to add the section with minimal concrete guidance or an explicit empty-state note\n    - Log: `⚠ Auto-fixed: Added missing section '{section}' to tasks\u002FREADME.md`\n\n**For kanban_board.md** (if exists):\n- Required sections:\n  - \"Linear Configuration\" (Team Name, UUID, Key)\n  - \"Work in Progress\" OR \"Epic Tracking\" (Kanban sections)\n- For each section:\n  - Check if section header exists\n  - **If missing:**\n    - Use Edit tool to add section with placeholder\n    - Log: `⚠ Auto-fixed: Added missing section '{section}' to kanban_board.md`\n\n### 2.3 Validate Maintenance section\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Search for `## Maintenance` header in last 20 lines\n2. **If missing:**\n   - Use Edit tool to add at end of file:\n     ```markdown\n     ## Maintenance\n\n     **Update Triggers:**\n     - When Linear workflow changes\n     - When task templates are added\u002Fmodified\n     - When label taxonomy changes\n\n     **Last Updated:** {current_date}\n     ```\n   - Log: `⚠ Auto-fixed: Added Maintenance section to {filename}`\n\n### 2.4 Validate POSIX line endings\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Check if file ends with single newline character\n2. **If missing:**\n   - Use Edit tool to add final newline\n   - Log: `⚠ Auto-fixed: Added POSIX newline to {filename}`\n\n### 2.5 Report validation summary\n\nLog summary:\n```\n✓ Structure validation completed:\n  tasks\u002FREADME.md:\n    - SCOPE tag: [added\u002Fpresent]\n    - Required sections: [count] sections [added\u002Fpresent]\n    - Maintenance section: [added\u002Fpresent]\n    - POSIX endings: [fixed\u002Fcompliant]\n  kanban_board.md:\n    - SCOPE tag: [added\u002Fpresent\u002Fskipped - file not exists]\n    - Required sections: [count] sections [added\u002Fpresent\u002Fskipped]\n    - Maintenance section: [added\u002Fpresent\u002Fskipped]\n    - POSIX endings: [fixed\u002Fcompliant\u002Fskipped]\n```\n\nIf violations found: `⚠ Auto-fixed {total} structural violations`\n\n**Output**: Structurally valid task management documentation\n\n---\n\n## Phase 3: Validate Content\n\n**Objective**: Ensure each section answers its validation questions with meaningful content. Special handling for Linear Configuration (placeholder detection, user prompts, UUID\u002FTeam Key validation).\n\n**When to execute**: After Phase 2 completes (structure valid, auto-fixes applied)\n\n**Process**:\n\n### 3.1 Load validation spec\n\n**MANDATORY READ:** Load `references\u002Fquestions.md` — parse sections and extract validation heuristics.\n\n### 3.2 Validate kanban_board.md → Linear Configuration (Special Handling)\n\n**Question**: \"What is the Linear team configuration?\"\n\n**Step 3.2.1: Check if kanban_board.md exists**:\n- Use Glob tool: `pattern: \"docs\u002Ftasks\u002Fkanban_board.md\"`\n- If NOT exists:\n  - Log: `ℹ kanban_board.md not found - skipping Linear Configuration validation`\n  - Skip to Step 3.3\n- If exists:\n  - Continue to Step 3.2.2\n\n**Step 3.2.2: Read Linear Configuration section**:\n- Read `docs\u002Ftasks\u002Fkanban_board.md`\n- Locate `## Linear Configuration` section\n- Extract Team Name, Team UUID, Team Key values\n\n**Step 3.2.3: Placeholder Detection**:\n\nCheck for placeholders:\n```\nPattern: [TEAM_NAME], [TEAM_UUID], [TEAM_KEY]\nIf ANY placeholder present → Interactive Setup Mode\nIf NO placeholders present → Validation Mode\n```\n\n**Interactive Setup Mode** (if placeholders detected):\n\n1. **Prompt user for Team Name**:\n   - Question: \"What is your Linear Team Name?\"\n   - Validation: Non-empty string\n   - Example: \"My Project Team\"\n\n2. **Prompt user for Team UUID**:\n   - Question: \"What is your Linear Team UUID?\"\n   - Format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`\n   - Validation Regex: `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`\n   - **If invalid:**\n     - Show error: \"Invalid UUID format. Expected: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (lowercase hex)\"\n     - Re-prompt user\n   - Example: \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\"\n\n3. **Prompt user for Team Key**:\n   - Question: \"What is your Linear Team Key (2-4 uppercase letters)?\"\n   - Format: 2-4 uppercase letters\n   - Validation Regex: `\u002F^[A-Z]{2,4}$\u002F`\n   - **If invalid:**\n     - Show error: \"Invalid Team Key format. Expected: 2-4 uppercase letters (e.g., PROJ, WEB, API)\"\n     - Re-prompt user\n   - Example: \"PROJ\"\n\n4. **Replace placeholders**:\n   - Use Edit tool to replace in kanban_board.md:\n     - `[TEAM_NAME]` → `{user_team_name}`\n     - `[TEAM_UUID]` → `{user_team_uuid}`\n     - `[TEAM_KEY]` → `{user_team_key}`\n     - `[WORKSPACE_URL]` → `https:\u002F\u002Flinear.app\u002F{workspace_slug}` (if placeholder exists)\n\n5. **Set initial counters** (if table exists):\n   - Set \"Next Epic Number\" → 1\n   - Set \"Next Story Number\" → 1\n\n6. **Update Last Updated date**:\n   - Replace `[YYYY-MM-DD]` → `{current_date}` in Maintenance section\n\n7. **Save updated kanban_board.md**\n\n8. **Log success**:\n   ```\n   ✓ Linear configuration updated:\n     - Team Name: {user_team_name}\n     - Team UUID: {user_team_uuid}\n     - Team Key: {user_team_key}\n     - Next Epic Number: 1\n     - Next Story Number: 1\n   ```\n\n**Validation Mode** (if real values present, no placeholders):\n\n1. **Extract existing values**:\n   - Extract Team UUID from line matching: `Team UUID: {value}` or in table\n   - Extract Team Key from line matching: `Team Key: {value}` or in table\n\n2. **Validate formats**:\n   - UUID: `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`\n   - Team Key: `\u002F^[A-Z]{2,4}$\u002F`\n\n3. **If validation fails**:\n   ```\n   ⚠ Invalid format detected in Linear Configuration:\n     - Team UUID: {uuid} (expected: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)\n     - Team Key: {key} (expected: 2-4 uppercase letters)\n\n   Fix manually or re-run skill to replace with correct values.\n   ```\n   - Mark as invalid but continue (don't block)\n\n4. **If validation passes**:\n   ```\n   ✓ Linear Configuration valid (Team: {name}, UUID: {uuid}, Key: {key})\n   ```\n\n### 3.3 Validate tasks\u002FREADME.md sections\n\n**Parametric loop for 3 questions** (from questions.md):\n\nFor each question in:\n1. \"How is Linear integrated into the task management system?\"\n2. \"What are the task state transitions and review criteria?\"\n3. \"What task templates are available and how to use them?\"\n\n**Validation process**:\n1. Extract validation heuristics from questions.md\n2. Read corresponding section content from tasks\u002FREADME.md\n3. Check if **ANY** heuristic passes:\n   - Contains keyword X → pass\n   - Has pattern Y → pass\n   - Length > N words → pass\n4. If ANY passes → Section valid\n5. If NONE passes → Log warning: `⚠ Section may be incomplete: {section_name}`\n\n**Example validation (Question 1: Linear Integration)**:\n```\nHeuristics:\n- Contains \"Linear\" or \"MCP\" → pass\n- Mentions team ID or UUID → pass\n- Has workflow states (Backlog, Todo, In Progress) → pass\n- Length > 100 words → pass\n\nCheck content:\n- ✓ Contains \"Linear\" → PASS\n→ Section valid\n```\n\n**No auto-discovery needed** (workflow is standardized in template)\n\n### 3.4 Validate kanban_board.md → Epic Tracking\n\n**Question**: \"Are Epics being tracked in the board?\"\n\n**If kanban_board.md exists**:\n\n**Validation heuristics**:\n```\n- Has \"Epic\" or \"Epics Overview\" section header → pass\n- Has table with columns: Epic, Name, Status, Progress → pass\n- OR has placeholder: \"No active epics\" → pass\n- Length > 20 words → pass\n```\n\n**Action**:\n1. Read Epic Tracking or Epics Overview section\n2. Check if ANY heuristic passes\n3. If passes → valid\n4. If none pass → log warning: `⚠ Epic Tracking section may be incomplete`\n\n**If kanban_board.md does NOT exist**:\n- Skip validation\n- Log: `ℹ Epic Tracking validation skipped (kanban_board.md not found)`\n\n### 3.5 Report content validation summary\n\nLog summary:\n```\n✓ Content validation completed:\n  tasks\u002FREADME.md:\n    - ✓ Linear Integration: valid (contains \"Linear\", \"MCP\", workflow states)\n    - ✓ Task Workflow: valid (contains state transitions)\n    - ✓ Task Templates: valid (contains template references)\n  kanban_board.md:\n    - ✓ Linear Configuration: {status} (Team: {name}, UUID: {uuid}, Key: {key})\n    - ✓ Epic Tracking: valid (table present or placeholder)\n```\n\n**Output**: Validated and potentially updated task management documentation with Linear configuration\n\n---\n\n## Complete Output Structure\n\n```\ndocs\u002F\n└── tasks\u002F\n    ├── README.md                     # Task management system rules\n    └── kanban_board.md               # Linear integration (optional, created manually or by other skills)\n```\n\n**Note**: Kanban board updated by ln-301-task-creator, ln-302-task-replanner, ln-400-story-executor (Epic Grouping logic).\n\n---\n\n## Reference Files\n\n- `references\u002Ftemplates\u002Ftasks_readme_template.md` — Task management system rules template\n- `references\u002Ftemplates\u002Fkanban_board_template.md` — Linear integration + kanban template\n- `references\u002Fquestions.md` — Validation questions, heuristics, special handling rules\n\n---\n\n## Critical Rules\n\n- **Idempotent:** Checks file existence before creation; preserves existing files; safe to re-run\n- **Linear UUID validation:** Team UUID must match `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`; Team Key must match `\u002F^[A-Z]{2,4}$\u002F`\n- **Shared docs-quality contract:** Follow `references\u002Fdocs_quality_contract.md` and `references\u002Fdocs_quality_rules.json` for placeholder policy, SCOPE\u002FMaintenance requirements, and allowed setup exceptions\n- **Placeholder detection:** If `[TEAM_NAME]`, `[TEAM_UUID]`, or `[TEAM_KEY]` found in kanban_board.md, enter interactive setup mode and prompt user; do not leave unresolved markers outside the allowlisted task docs\n- **Shared opening contract required:** Both README.md and kanban_board.md must include `SCOPE`, metadata markers, `Quick Navigation`, `Agent Entry`, and `Maintenance`\n- **Story-Level Test Task Pattern:** Tests consolidated in final Story task, not scattered across implementation tasks\n\n## Return Contract\n\nReturn a normalized summary so `ln-100` can run a centralized docs-quality gate without re-parsing worker prose:\n\n```json\n{\n  \"created_files\": [\n    \"docs\u002Ftasks\u002FREADME.md\",\n    \"docs\u002Ftasks\u002Fkanban_board.md\"\n  ],\n  \"skipped_files\": [],\n  \"quality_inputs\": {\n    \"doc_paths\": [\n      \"docs\u002Ftasks\u002FREADME.md\",\n      \"docs\u002Ftasks\u002Fkanban_board.md\"\n    ],\n    \"owners\": {\n      \"docs\u002Ftasks\u002FREADME.md\": \"ln-130-tasks-docs-creator\",\n      \"docs\u002Ftasks\u002Fkanban_board.md\": \"ln-130-tasks-docs-creator\"\n    }\n  },\n  \"validation_status\": \"passed|passed_with_fixes|skipped\"\n}\n```\n\n## Runtime Summary Artifact\n\n**MANDATORY READ:** Load `references\u002Fdocs_generation_summary_contract.md`\n\nAccept optional `summaryArtifactPath`.\n\nSummary kind:\n- `docs-generation`\n\nRequired payload semantics:\n- `worker = \"ln-130\"`\n- `status`\n- `created_files`\n- `skipped_files`\n- `quality_inputs`\n- `validation_status`\n- `warnings`\n\nWrite the summary to the provided artifact path or return the same envelope in structured output.\n\n## Definition of Done\n\n- [ ] Phase 1: tasks\u002FREADME.md created from template (or preserved if exists); setup placeholders contained only within allowlisted task docs\n- [ ] Phase 2: Structure valid — SCOPE tags, required sections, Maintenance, POSIX endings (auto-fixed if needed)\n- [ ] Phase 3: Content valid — heuristics pass per questions.md, Tracker Configuration set up (if placeholders found)\n- [ ] Return contract emitted with `created_files`, `skipped_files`, `quality_inputs`, and `validation_status`\n- [ ] Summary message displayed with auto-fix count and Tracker Configuration status\n\n---\n\n**Version:** 7.1.0\n**Last Updated:** 2025-01-12\n","> **Paths:** File paths (`references\u002F`, `..\u002Fln-*`) are relative to this skill directory.\n\n**Type:** L2 Worker\n**Category:** 1XX Documentation Pipeline\n\n# Tasks Documentation Creator\n\nThis skill creates task management documentation: docs\u002Ftasks\u002FREADME.md (task management system rules) and docs\u002Ftasks\u002Fkanban_board.md (configured tracker integration with Epic Story Counters).\n\n## Purpose\n\nCreate and validate task management documentation (docs\u002Ftasks\u002F). Generates README.md with workflow rules and kanban_board.md with tracker integration that adapts to the configured provider (linear\u002Fgithub\u002Ffile), including interactive setup for provider-specific configuration.\n\n## When to Use This Skill\n\n**This skill is a L2 WORKER** invoked by **ln-100-documents-pipeline** orchestrator OR used standalone.\n\nUse this skill when:\n- Creating task management documentation (docs\u002Ftasks\u002F)\n- Setting up tracker integration and kanban board\n- Validating existing task documentation structure and content\n- Configuring provider-specific tracker settings (linear: Team Name\u002FUUID\u002FKey; github: repository\u002Fproject_number; file: nothing)\n\n**Part of workflow**: ln-100-documents-pipeline → ln-110-project-docs-coordinator → ln-120-reference-docs-creator → **ln-130-tasks-docs-creator** → ln-140-test-docs-creator (optional)\n\n## Workflow\n\nThe skill follows a **3-phase workflow**: CREATE → VALIDATE STRUCTURE → VALIDATE CONTENT.\n\n**MANDATORY READ:** Load `references\u002Fdocs_quality_contract.md`, and `references\u002Fmarkdown_read_protocol.md`.\nOptional rule catalog: load `references\u002Fdocs_quality_rules.json` only when exact rule IDs, path matrices, or allowlisted placeholder exceptions are needed.\n\n**Phase 1: CREATE** - Create tasks\u002FREADME.md from template with SCOPE tags, workflow rules, configured tracker integration\n**Phase 2: VALIDATE STRUCTURE** - Auto-fix structural violations (SCOPE tags, sections, Maintenance, POSIX)\n**Phase 3: VALIDATE CONTENT** - Validate semantic content + provider-conditional Tracker Configuration handling (placeholder detection, provider-specific field validation, interactive user prompts). Raw placeholders are allowed only during setup for `docs\u002Ftasks\u002FREADME.md` and `docs\u002Ftasks\u002Fkanban_board.md`; published output must not leak unresolved markers into any other document.\n\n---\n\n## Phase 1: Create tasks\u002FREADME.md\n\n**Objective**: Create task management system documentation from template.\n\n**When to execute**: Always (first phase)\n\n**Process**:\n\n1. **Check if tasks\u002FREADME.md exists**:\n   - Use Glob tool: `pattern: \"docs\u002Ftasks\u002FREADME.md\"`\n   - If file exists:\n     - Skip creation\n     - Log: `✓ docs\u002Ftasks\u002FREADME.md already exists (preserved)`\n     - Proceed to Phase 2\n   - If NOT exists:\n     - Continue to step 2\n\n2. **Create tasks directory**:\n   - Create the `docs\u002Ftasks\u002F` directory if it doesn't exist\n\n3. **Create tasks\u002FREADME.md from template**:\n   - **MANDATORY READ:** Load `references\u002Ftemplates\u002Ftasks_readme_template.md`\n   - Copy template → `docs\u002Ftasks\u002FREADME.md`\n   - Replace placeholders:\n     - `{{DATE}}` → current date (YYYY-MM-DD)\n   - Template contains:\n     - Full shared header contract (`SCOPE`, `DOC_KIND`, `DOC_ROLE`, `READ_WHEN`, `SKIP_WHEN`, `PRIMARY_SOURCES`)\n     - Story-Level Test Task Pattern\n     - Kanban Board Structure (Epic Grouping Pattern)\n     - Linear Integration (MCP methods)\n     - Quick Navigation, Agent Entry, and Maintenance sections\n\n4. **Notify user**:\n   - If created: `✓ Created docs\u002Ftasks\u002FREADME.md with task management rules`\n   - If skipped: `✓ docs\u002Ftasks\u002FREADME.md already exists (preserved)`\n\n**Output**: docs\u002Ftasks\u002FREADME.md (created or existing)\n\n---\n\n## Phase 2: Validate Structure\n\n**Objective**: Ensure tasks\u002FREADME.md and kanban_board.md comply with structural requirements. Auto-fix violations.\n\n**When to execute**: After Phase 1 completes (files exist or created)\n\n**Process**:\n\n### 2.1 Validate SCOPE tags\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Read the opening block\n2. Check for `\u003C!-- SCOPE: ... -->` tag and metadata markers\n3. Expected values:\n   - tasks\u002FREADME.md: `\u003C!-- SCOPE: Task tracking system workflow and rules ONLY -->`\n   - kanban_board.md: `\u003C!-- SCOPE: Quick navigation to active tasks in Linear -->`\n4. **If missing:**\n   - Use Edit tool to add SCOPE tag after first heading\n   - Log: `⚠ Auto-fixed: Added missing SCOPE tag to {filename}`\n\n### 2.2 Validate required sections\n\n**MANDATORY READ:** Load `references\u002Fquestions.md` for validation specs (section names, heuristics, special handling rules).\n\n**For tasks\u002FREADME.md**:\n- Required sections (from questions.md):\n  - \"Linear Integration\" OR \"Core Concepts\" (Linear MCP methods)\n  - \"Task Workflow\" OR \"Critical Rules\" (state transitions)\n  - \"Task Templates\" (template references)\n- For each section:\n  - Check if section header exists (case-insensitive)\n  - **If missing:**\n    - Use Edit tool to add the section with minimal concrete guidance or an explicit empty-state note\n    - Log: `⚠ Auto-fixed: Added missing section '{section}' to tasks\u002FREADME.md`\n\n**For kanban_board.md** (if exists):\n- Required sections:\n  - \"Linear Configuration\" (Team Name, UUID, Key)\n  - \"Work in Progress\" OR \"Epic Tracking\" (Kanban sections)\n- For each section:\n  - Check if section header exists\n  - **If missing:**\n    - Use Edit tool to add section with placeholder\n    - Log: `⚠ Auto-fixed: Added missing section '{section}' to kanban_board.md`\n\n### 2.3 Validate Maintenance section\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Search for `## Maintenance` header in last 20 lines\n2. **If missing:**\n   - Use Edit tool to add at end of file:\n     ```markdown\n     ## Maintenance\n\n     **Update Triggers:**\n     - When Linear workflow changes\n     - When task templates are added\u002Fmodified\n     - When label taxonomy changes\n\n     **Last Updated:** {current_date}\n     ```\n   - Log: `⚠ Auto-fixed: Added Maintenance section to {filename}`\n\n### 2.4 Validate POSIX line endings\n\n**Files to check**: docs\u002Ftasks\u002FREADME.md, docs\u002Ftasks\u002Fkanban_board.md (if exists)\n\nFor each file:\n1. Check if file ends with single newline character\n2. **If missing:**\n   - Use Edit tool to add final newline\n   - Log: `⚠ Auto-fixed: Added POSIX newline to {filename}`\n\n### 2.5 Report validation summary\n\nLog summary:\n```\n✓ Structure validation completed:\n  tasks\u002FREADME.md:\n    - SCOPE tag: [added\u002Fpresent]\n    - Required sections: [count] sections [added\u002Fpresent]\n    - Maintenance section: [added\u002Fpresent]\n    - POSIX endings: [fixed\u002Fcompliant]\n  kanban_board.md:\n    - SCOPE tag: [added\u002Fpresent\u002Fskipped - file not exists]\n    - Required sections: [count] sections [added\u002Fpresent\u002Fskipped]\n    - Maintenance section: [added\u002Fpresent\u002Fskipped]\n    - POSIX endings: [fixed\u002Fcompliant\u002Fskipped]\n```\n\nIf violations found: `⚠ Auto-fixed {total} structural violations`\n\n**Output**: Structurally valid task management documentation\n\n---\n\n## Phase 3: Validate Content\n\n**Objective**: Ensure each section answers its validation questions with meaningful content. Special handling for Linear Configuration (placeholder detection, user prompts, UUID\u002FTeam Key validation).\n\n**When to execute**: After Phase 2 completes (structure valid, auto-fixes applied)\n\n**Process**:\n\n### 3.1 Load validation spec\n\n**MANDATORY READ:** Load `references\u002Fquestions.md` — parse sections and extract validation heuristics.\n\n### 3.2 Validate kanban_board.md → Linear Configuration (Special Handling)\n\n**Question**: \"What is the Linear team configuration?\"\n\n**Step 3.2.1: Check if kanban_board.md exists**:\n- Use Glob tool: `pattern: \"docs\u002Ftasks\u002Fkanban_board.md\"`\n- If NOT exists:\n  - Log: `ℹ kanban_board.md not found - skipping Linear Configuration validation`\n  - Skip to Step 3.3\n- If exists:\n  - Continue to Step 3.2.2\n\n**Step 3.2.2: Read Linear Configuration section**:\n- Read `docs\u002Ftasks\u002Fkanban_board.md`\n- Locate `## Linear Configuration` section\n- Extract Team Name, Team UUID, Team Key values\n\n**Step 3.2.3: Placeholder Detection**:\n\nCheck for placeholders:\n```\nPattern: [TEAM_NAME], [TEAM_UUID], [TEAM_KEY]\nIf ANY placeholder present → Interactive Setup Mode\nIf NO placeholders present → Validation Mode\n```\n\n**Interactive Setup Mode** (if placeholders detected):\n\n1. **Prompt user for Team Name**:\n   - Question: \"What is your Linear Team Name?\"\n   - Validation: Non-empty string\n   - Example: \"My Project Team\"\n\n2. **Prompt user for Team UUID**:\n   - Question: \"What is your Linear Team UUID?\"\n   - Format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`\n   - Validation Regex: `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`\n   - **If invalid:**\n     - Show error: \"Invalid UUID format. Expected: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (lowercase hex)\"\n     - Re-prompt user\n   - Example: \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\"\n\n3. **Prompt user for Team Key**:\n   - Question: \"What is your Linear Team Key (2-4 uppercase letters)?\"\n   - Format: 2-4 uppercase letters\n   - Validation Regex: `\u002F^[A-Z]{2,4}$\u002F`\n   - **If invalid:**\n     - Show error: \"Invalid Team Key format. Expected: 2-4 uppercase letters (e.g., PROJ, WEB, API)\"\n     - Re-prompt user\n   - Example: \"PROJ\"\n\n4. **Replace placeholders**:\n   - Use Edit tool to replace in kanban_board.md:\n     - `[TEAM_NAME]` → `{user_team_name}`\n     - `[TEAM_UUID]` → `{user_team_uuid}`\n     - `[TEAM_KEY]` → `{user_team_key}`\n     - `[WORKSPACE_URL]` → `https:\u002F\u002Flinear.app\u002F{workspace_slug}` (if placeholder exists)\n\n5. **Set initial counters** (if table exists):\n   - Set \"Next Epic Number\" → 1\n   - Set \"Next Story Number\" → 1\n\n6. **Update Last Updated date**:\n   - Replace `[YYYY-MM-DD]` → `{current_date}` in Maintenance section\n\n7. **Save updated kanban_board.md**\n\n8. **Log success**:\n   ```\n   ✓ Linear configuration updated:\n     - Team Name: {user_team_name}\n     - Team UUID: {user_team_uuid}\n     - Team Key: {user_team_key}\n     - Next Epic Number: 1\n     - Next Story Number: 1\n   ```\n\n**Validation Mode** (if real values present, no placeholders):\n\n1. **Extract existing values**:\n   - Extract Team UUID from line matching: `Team UUID: {value}` or in table\n   - Extract Team Key from line matching: `Team Key: {value}` or in table\n\n2. **Validate formats**:\n   - UUID: `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`\n   - Team Key: `\u002F^[A-Z]{2,4}$\u002F`\n\n3. **If validation fails**:\n   ```\n   ⚠ Invalid format detected in Linear Configuration:\n     - Team UUID: {uuid} (expected: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)\n     - Team Key: {key} (expected: 2-4 uppercase letters)\n\n   Fix manually or re-run skill to replace with correct values.\n   ```\n   - Mark as invalid but continue (don't block)\n\n4. **If validation passes**:\n   ```\n   ✓ Linear Configuration valid (Team: {name}, UUID: {uuid}, Key: {key})\n   ```\n\n### 3.3 Validate tasks\u002FREADME.md sections\n\n**Parametric loop for 3 questions** (from questions.md):\n\nFor each question in:\n1. \"How is Linear integrated into the task management system?\"\n2. \"What are the task state transitions and review criteria?\"\n3. \"What task templates are available and how to use them?\"\n\n**Validation process**:\n1. Extract validation heuristics from questions.md\n2. Read corresponding section content from tasks\u002FREADME.md\n3. Check if **ANY** heuristic passes:\n   - Contains keyword X → pass\n   - Has pattern Y → pass\n   - Length > N words → pass\n4. If ANY passes → Section valid\n5. If NONE passes → Log warning: `⚠ Section may be incomplete: {section_name}`\n\n**Example validation (Question 1: Linear Integration)**:\n```\nHeuristics:\n- Contains \"Linear\" or \"MCP\" → pass\n- Mentions team ID or UUID → pass\n- Has workflow states (Backlog, Todo, In Progress) → pass\n- Length > 100 words → pass\n\nCheck content:\n- ✓ Contains \"Linear\" → PASS\n→ Section valid\n```\n\n**No auto-discovery needed** (workflow is standardized in template)\n\n### 3.4 Validate kanban_board.md → Epic Tracking\n\n**Question**: \"Are Epics being tracked in the board?\"\n\n**If kanban_board.md exists**:\n\n**Validation heuristics**:\n```\n- Has \"Epic\" or \"Epics Overview\" section header → pass\n- Has table with columns: Epic, Name, Status, Progress → pass\n- OR has placeholder: \"No active epics\" → pass\n- Length > 20 words → pass\n```\n\n**Action**:\n1. Read Epic Tracking or Epics Overview section\n2. Check if ANY heuristic passes\n3. If passes → valid\n4. If none pass → log warning: `⚠ Epic Tracking section may be incomplete`\n\n**If kanban_board.md does NOT exist**:\n- Skip validation\n- Log: `ℹ Epic Tracking validation skipped (kanban_board.md not found)`\n\n### 3.5 Report content validation summary\n\nLog summary:\n```\n✓ Content validation completed:\n  tasks\u002FREADME.md:\n    - ✓ Linear Integration: valid (contains \"Linear\", \"MCP\", workflow states)\n    - ✓ Task Workflow: valid (contains state transitions)\n    - ✓ Task Templates: valid (contains template references)\n  kanban_board.md:\n    - ✓ Linear Configuration: {status} (Team: {name}, UUID: {uuid}, Key: {key})\n    - ✓ Epic Tracking: valid (table present or placeholder)\n```\n\n**Output**: Validated and potentially updated task management documentation with Linear configuration\n\n---\n\n## Complete Output Structure\n\n```\ndocs\u002F\n└── tasks\u002F\n    ├── README.md                     # Task management system rules\n    └── kanban_board.md               # Linear integration (optional, created manually or by other skills)\n```\n\n**Note**: Kanban board updated by ln-301-task-creator, ln-302-task-replanner, ln-400-story-executor (Epic Grouping logic).\n\n---\n\n## Reference Files\n\n- `references\u002Ftemplates\u002Ftasks_readme_template.md` — Task management system rules template\n- `references\u002Ftemplates\u002Fkanban_board_template.md` — Linear integration + kanban template\n- `references\u002Fquestions.md` — Validation questions, heuristics, special handling rules\n\n---\n\n## Critical Rules\n\n- **Idempotent:** Checks file existence before creation; preserves existing files; safe to re-run\n- **Linear UUID validation:** Team UUID must match `\u002F^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$\u002F`; Team Key must match `\u002F^[A-Z]{2,4}$\u002F`\n- **Shared docs-quality contract:** Follow `references\u002Fdocs_quality_contract.md` and `references\u002Fdocs_quality_rules.json` for placeholder policy, SCOPE\u002FMaintenance requirements, and allowed setup exceptions\n- **Placeholder detection:** If `[TEAM_NAME]`, `[TEAM_UUID]`, or `[TEAM_KEY]` found in kanban_board.md, enter interactive setup mode and prompt user; do not leave unresolved markers outside the allowlisted task docs\n- **Shared opening contract required:** Both README.md and kanban_board.md must include `SCOPE`, metadata markers, `Quick Navigation`, `Agent Entry`, and `Maintenance`\n- **Story-Level Test Task Pattern:** Tests consolidated in final Story task, not scattered across implementation tasks\n\n## Return Contract\n\nReturn a normalized summary so `ln-100` can run a centralized docs-quality gate without re-parsing worker prose:\n\n```json\n{\n  \"created_files\": [\n    \"docs\u002Ftasks\u002FREADME.md\",\n    \"docs\u002Ftasks\u002Fkanban_board.md\"\n  ],\n  \"skipped_files\": [],\n  \"quality_inputs\": {\n    \"doc_paths\": [\n      \"docs\u002Ftasks\u002FREADME.md\",\n      \"docs\u002Ftasks\u002Fkanban_board.md\"\n    ],\n    \"owners\": {\n      \"docs\u002Ftasks\u002FREADME.md\": \"ln-130-tasks-docs-creator\",\n      \"docs\u002Ftasks\u002Fkanban_board.md\": \"ln-130-tasks-docs-creator\"\n    }\n  },\n  \"validation_status\": \"passed|passed_with_fixes|skipped\"\n}\n```\n\n## Runtime Summary Artifact\n\n**MANDATORY READ:** Load `references\u002Fdocs_generation_summary_contract.md`\n\nAccept optional `summaryArtifactPath`.\n\nSummary kind:\n- `docs-generation`\n\nRequired payload semantics:\n- `worker = \"ln-130\"`\n- `status`\n- `created_files`\n- `skipped_files`\n- `quality_inputs`\n- `validation_status`\n- `warnings`\n\nWrite the summary to the provided artifact path or return the same envelope in structured output.\n\n## Definition of Done\n\n- [ ] Phase 1: tasks\u002FREADME.md created from template (or preserved if exists); setup placeholders contained only within allowlisted task docs\n- [ ] Phase 2: Structure valid — SCOPE tags, required sections, Maintenance, POSIX endings (auto-fixed if needed)\n- [ ] Phase 3: Content valid — heuristics pass per questions.md, Tracker Configuration set up (if placeholders found)\n- [ ] Return contract emitted with `created_files`, `skipped_files`, `quality_inputs`, and `validation_status`\n- [ ] Summary message displayed with auto-fix count and Tracker Configuration status\n\n---\n\n**Version:** 7.1.0\n**Last Updated:** 2025-01-12\n",{"name":5,"model":49,"license":15,"description":7},"claude-sonnet-4-6","main","fbfb242f793fdf040f3a1a6b100896c188c228c8","_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator",1,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvitalikpestov","Listing on crypto exchanges","2026-06-15 22:12:56",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add vitalikpestov\u002FSkills-Catalog --skill ln-130-tasks-docs-creator",{"tool":64,"command":65},"bunx","bunx skills add vitalikpestov\u002FSkills-Catalog --skill ln-130-tasks-docs-creator",{"tool":67,"command":68},"pnpm","pnpm dlx skills add vitalikpestov\u002FSkills-Catalog --skill ln-130-tasks-docs-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcoordinator_summary_contract.md","REFERENCE","参考文档",1009,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fcoordinator_summary_contract.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fdocs_generation_summary_contract.md",535,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fdocs_generation_summary_contract.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fdocs_quality_contract.md",2236,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fdocs_quality_contract.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdocs_quality_rules.json",8029,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fdocs_quality_rules.json",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdocs_quality_rules.json.SOURCE.md",1283,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fdocs_quality_rules.json.SOURCE.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fmarkdown_read_protocol.md",1505,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fmarkdown_read_protocol.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fquestions.md",7684,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fquestions.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstorage_mode_detection.md",2042,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Fstorage_mode_detection.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Ftemplates\u002Fkanban_board_template.md",4851,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Ftemplates\u002Fkanban_board_template.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftemplates\u002Ftasks_readme_template.md",14775,"https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_AI-Automation\u002Fclaude-code-skills-levnikolaevich\u002Fplugins\u002Fdocumentation-pipeline\u002Fskills\u002Fln-130-tasks-docs-creator\u002Freferences\u002Ftemplates\u002Ftasks_readme_template.md",[115,155,179,196,218,251],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":133,"publishedAt":154},"01M71V1MC994P553631JZSWVYD","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Web3\u002Fsolana-dev\u002Fskill\u002FSKILL.md",[121,124,127,128],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153],"dev","solana dev","solana","Wallet","search","testing","solana cli","kit","MCP","web3","react","create","server","write","playbook","live","security","ui","concepts","toolchain","2026-11-10 13:02:02",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":154},"01M71TYQPHE2YGKTT7DG9QCW3K","generating-trading-signals","Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.).\nCombines multiple indicators into composite signals with confidence scores.\nUse when analyzing assets for trading opportunities or checking technical indicators.\nTrigger with phrases like \"get trading signals\", \"check indicators\", \"analyze for entry\",\n\"scan for opportunities\", \"generate buy\u002Fsell signals\", or \"technical analysis\".","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002Fgenerating-trading-signals\u002FSKILL.md",[],[162,163,164,165,166,167,33,168,169,170,171,172,40,32,173,174,175,176,177,178],"generating trading signals","signals","trading signals","trading","get","technical indicators","scan","rsi","trigger","python","technical","Bash","analysis","code","io","check","analyze",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":154},"01M71TY4CR3GKGQ3M12X9WN95Y","prediction-monitor","Prediction Monitor - Auto-activating skill for ML Deployment.\nTriggers on: prediction monitor, prediction monitor\nPart of the ML Deployment skill category.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Trading-Finance\u002FAI Predictions\u002Fprediction-monitor\u002FSKILL.md",[],[186,187,188,33,189,190,147,191,192,193,194,195,173],"prediction","monitor","prediction monitor","deployment","read","edit","triggers","grep","auto","ml",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":154},"01M71TXD9MYXZC39HCPP909HTZ","strategy-advisor","High-level strategic thinking and business decision guidance for planning and direction-setting.\nUse when: making strategic decisions, evaluating business options, setting direction, analyzing\ntrade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Fstrategy-advisor\u002FSKILL.md",[],[203,204,205,206,31,207,208,209,210,33,211,212,213,40,214,215,32,216,174,217],"strategy advisor","strategy","advisor","competitive","thinking","planning","direction","trade-offs","long","decision","strategic","business","apps","decisions","trade",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":222,"sourceHtmlUrl":223,"categories":224,"keywords":231,"publishedAt":154},"01M71TWHBT2R1P1FNWTW67ZREP","app-paywall-pilot","Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans\u002Fprices\u002Ftrials, review RevenueCat\u002FAdapty\u002FApphud\u002FSuperwall setup, calculate LTV\u002FROAS, or build paywall implementation.","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffrom-dosesync\u002Fapp-paywall-pilot\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":229,"categoryName":230,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000032","设计师",[232,233,234,235,236,237,238,239,240,241,242,243,32,244,245,246,247,248,249,250],"app","paywall","app paywall pilot","paid","paywalls","prices","choose","flows","fix","improve","design","app store","review","audit","ux","subscription","mobile","my","calculate",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":255,"licenseFileUrl":256,"sourceHtmlUrl":257,"categories":258,"keywords":261,"publishedAt":154},"01M71TWET8GFKEB7ZHJPMQX29V","figma","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fvitalikpestov\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F_Product-Apps\u002Ffigma\u002FSKILL.md",[259,260],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":229,"categoryName":230,"taxonomyType":131,"taxonomyTypeDesc":132},[253,262,263,264,265,170,242,142,40,32,266,267,175,30,146,268,269,270,271,272],"fetch","ids","mcp setup","translate","mcp server","Variables","Nodes","figma mcp","code implementation","node","assets"]