zhongwei/gh-levnikolaevich-claude-code-skills-full-development-workflow-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-30 08:37:27 +08:00
commit 37774aa937
131 changed files with 31137 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
skills/ln-331-task-executor/SKILL.md Normal file
View File

@@ -0,0 +1,46 @@
---
name: ln-331-task-executor
description: Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks.
---
# Implementation Task Executor
Executes a single implementation (or refactor) task from Todo to To Review using the task description and linked guides.
## Purpose & Scope
- Handle one selected task only; never touch other tasks.
- Follow task Technical Approach/plan/AC; apply KISS/YAGNI and guide patterns.
- Update Linear/kanban for this task: Todo -> In Progress -> To Review.
- Run typecheck/lint; update docs/tests/config per task instructions.
- Not for test tasks (label "tests" goes to ln-334-test-executor).
## Workflow (concise)
1) **Load context:** Fetch full task description; read linked guides/manuals/ADRs; auto-discover team/config if needed.
2) **Pick task:** If ID provided, use it; otherwise list Todo tasks and select one.
3) **Start work:** Update this task to In Progress in Linear; move it in kanban (keep Epic/Story indent).
4) **Implement:** Follow checkboxes/plan; keep it simple; avoid hardcoded values; reuse existing components; update docs noted in Affected Components; update existing tests if impacted (no new tests here).
5) **Quality:** Run typecheck and lint (or project equivalents); ensure instructions in Existing Code Impact are addressed.
6) **Finish:** Mark task To Review in Linear; update kanban to To Review; add summary comment (what changed, tests run, docs touched).
## Critical Rules
- Single-task updates only; no bulk status changes.
- Keep language of the task (EN/RU) in edits/comments.
- No code snippets in the description; code lives in repo, not in Linear.
- No new test creation; only update existing tests if required.
- Preserve Foundation-First ordering from orchestrator; do not reorder tasks.
## Definition of Done
- Task selected and set to In Progress; kanban updated accordingly.
- Guides/manuals/ADRs read; approach aligned with task Technical Approach.
- Implementation completed per plan/AC; docs and impacted tests updated.
- Typecheck and lint passed (or project quality commands) with evidence in comment.
- Task set to To Review; kanban moved to To Review; summary comment added.
## Reference Files
- Task template: `../ln-311-task-creator/references/task_template_implementation.md`
- Guides/manuals/ADRs: `docs/guides/`, `docs/manuals/`, `docs/adrs/`
- Kanban format: `docs/tasks/kanban_board.md`
---
Version: 5.1.0 (Condensed executor flow and single-task safety)
Last Updated: 2025-11-26

58
skills/ln-331-task-executor/diagram.html Normal file
View File

@@ -0,0 +1,58 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>ln-331-task-executor - State Diagram</title>
<script src="https://cdn.jsdelivr.net/npm/mermaid@10/dist/mermaid.min.js"></script>
<link rel="stylesheet" href="../shared/css/diagram.css">
</head>
<body>
<div class="container">
<header>
<h1>⚙️ ln-331-task-executor</h1>
<p class="subtitle">Implementation Task Executor - State Diagram</p>
</header>
<div class="info-box">
<h3>📋 Overview</h3>
<ul>
<li><strong>Purpose:</strong> Execute implementation tasks ONLY (NOT test tasks)</li>
<li><strong>State Transition:</strong> Todo → In Progress → To Review</li>
<li><strong>Principles:</strong> KISS/YAGNI, read guides from Technical Approach</li>
</ul>
</div>
<div class="diagram-container">
<div class="mermaid">
graph TD
Start([Start: Execute Implementation Task]) --> Phase1[Phase 1: Read Referenced Guides<br/>Extract guide links from Technical Approach]
Phase1 --> Phase2[Phase 2: Discovery<br/>Team ID auto-discovery]
Phase2 --> Phase3[Phase 3: Preparation<br/>Load task Todo<br/>Update status: Todo → In Progress]
Phase3 --> Phase4[Phase 4: Implementation<br/>Follow checkboxes<br/>KISS/YAGNI principles<br/>Apply guide patterns<br/>Address Existing Code Impact]
Phase4 --> Phase5[Phase 5: Quality Gates<br/>Type checking<br/>Lint]
Phase5 --> QualityPass{Quality gates<br/>pass?}
QualityPass -->|No| Phase4
QualityPass -->|Yes| Phase6
Phase6[Phase 5: Handoff<br/>Comment in Linear<br/>Update status: In Progress → To Review]
Phase6 --> AllTasksCheck{All Story tasks<br/>To Review or Done?}
AllTasksCheck -->|Yes| UpdateStory[Update Story status if needed]
AllTasksCheck -->|No| End
UpdateStory --> End([End])
classDef discovery fill:#E3F2FD,stroke:#1976D2,stroke-width:2px
classDef processing fill:#FFF9C4,stroke:#F57C00,stroke-width:2px
classDef decision fill:#FFE0B2,stroke:#E64A19,stroke-width:2px
classDef action fill:#C8E6C9,stroke:#388E3C,stroke-width:2px
class Phase1,Phase2 discovery
class Phase3,Phase4,Phase5 processing
class QualityPass,AllTasksCheck decision
class Phase6,UpdateStory action
</div>
</div>
<footer>
<p>ln-331-task-executor | Chat prefix: ⚙️ [EXECUTOR]</p>
</footer>
</div>
<script>
mermaid.initialize({ startOnLoad: true, theme: 'default', flowchart: { useMaxWidth: true, htmlLabels: true, curve: 'basis' } });
</script>
</body>
</html>