Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[70] CLOSE. Manage task lifecycle with correct statuses and no duplicates. Ensure each task has one status, artifacts match claims, and no task appears in multiple places. Use when managing task lists, updating progress, or ensuring task tracking integrity across systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Core Principle: One task, one status, one location. Status matches reality. Artifacts prove completion. No duplicates anywhere.
When you invoke this skill, you're asking AI to:
| Dimension | 100% Core | +50% Enhancement |
|---|---|---|
| Status | Correct state | + Transition reason documented |
| Artifacts | Match status | + Quality verified |
| Duplicates | None found | + Cross-system check |
| Audit | Changes logged | + Full history preserved |
🔥 ACTIVE WORKFLOW
├── Pending: Task defined but not started
├── In Progress: Currently being worked on
├── Blocked: Waiting for dependencies
└── Review: Ready for verification
✅ COMPLETION WORKFLOW
├── Completed: Successfully finished
├── Verified: Quality checks passed
├── Archived: Moved to long-term storage
└── Cancelled: No longer needed
Valid Transitions:
Pending → In Progress (work started)
Pending → Cancelled (no longer needed)
In Progress → Blocked (waiting on dependency)
In Progress → Review (ready for check)
In Progress → Cancelled (abandoned)
Blocked → In Progress (blocker resolved)
Blocked → Cancelled (no longer needed)
Review → In Progress (changes requested)
Review → Completed (approved)
Review → Cancelled (rejected entirely)
Completed → Verified (quality confirmed)
Completed → In Progress (issues found)
Verified → Archived (stored long-term)
📋 **TASK STATE CHECK**
**Task:** [Task ID and title]
**Current Status:** [What system says]
**Actual State:** [What reality shows]
**Match:** ✅ Aligned | ❌ Mismatch
📦 **ARTIFACT CHECK**
**Status Claimed:** [e.g., Completed]
**Artifacts Required:** [What should exist]
**Artifacts Found:**
- [ ] [Artifact 1]: [Exists/Missing]
- [ ] [Artifact 2]: [Exists/Missing]
**Alignment:** ✅ Match | ❌ Gap
🔍 **DUPLICATE SCAN**
**Locations Checked:**
- [ ] [System 1]: [Found/Not Found]
- [ ] [System 2]: [Found/Not Found]
- [ ] [System 3]: [Found/Not Found]
**Duplicates Found:** [None / List them]
**Action Required:** [None / Consolidate]
🔄 **STATUS UPDATE**
**From:** [Previous status]
**To:** [New status]
**Reason:** [Why changing]
**Valid Transition:** ✅ Yes | ❌ No
**Changes Made:**
- [System 1]: Updated
- [Artifacts]: Verified
- [Documentation]: Logged
✅ **INTEGRITY VERIFIED**
**Single Status:** ✅ One status only
**Artifacts Match:** ✅ Deliverables align
**No Duplicates:** ✅ Single location
**Audit Trail:** ✅ Change documented
For status updates:
📋 **TASK-TRACK 150 UPDATE**
**Task:** [ID] — [Title]
**Status Change:**
├── From: [Previous]
├── To: [New]
└── Reason: [Why]
**Artifacts:**
├── 📄 [Deliverable 1]: [Location] ✅
├── 📊 [Deliverable 2]: [Location] ✅
└── Coverage: [X]%
**Integrity:**
├── Single Status: ✅
├── Artifacts Match: ✅
├── No Duplicates: ✅
└── Audit Logged: ✅
**Confirmation Required?** [Yes/No]
For integrity audits:
🔍 **TASK-TRACK 150 AUDIT**
**Scope:** [What was checked]
**Findings:**
├── Tasks Checked: [N]
├── Status Correct: [N] ✅
├── Status Mismatch: [N] ⚠️
├── Duplicates Found: [N] 🔴
└── Missing Artifacts: [N] ⚠️
**Issues:**
1. [Task X]: [Problem] → [Fix]
2. [Task Y]: [Problem] → [Fix]
**Actions Taken:**
- [Action 1]
- [Action 2]
**System Integrity:** [✅ Clean | ⚠️ Issues Fixed | 🔴 Needs Attention]
🔥 **[ID] — [Task Title]**
**Status:** [Current State] | **Priority:** [Level]
**Created:** [Date] | **Due:** [Date]
**Progress:**
- [x] Step 1: [Description] ✅ [Date]
- [x] Step 2: [Description] ✅ [Date]
- [ ] Step 3: [Description]
**Artifacts:**
- 📄 [Deliverable 1]: [Location/Link]
- 📊 [Deliverable 2]: [Location/Link]
**Blockers:** [None / List]
**Notes:** [Updates, context, next steps]
| Failure | Detection | Recovery |
|---|---|---|
| Duplicate Tasks | Same task in multiple places | Consolidate, remove duplicates |
| Status Mismatch | Status doesn't match artifacts | Correct status or complete work |
| Lifecycle Violation | Invalid state transition | Return to correct state |
| Missing Audit | No change documentation | Document all changes now |
Task UT-015:
- In "Active" section: "In Progress"
- In "Completed" section: "Done"
- In sprint board: "Review"
Result: Confusion, task worked on twice, wasted effort
📋 TASK-TRACK 150 UPDATE
Task: UT-015 — Implement user authentication
Status Change:
├── From: In Progress
├── To: Completed
└── Reason: All acceptance criteria met, tests passing
Artifacts:
├── 📄 auth.service.ts: /src/services/ ✅
├── 📊 auth.test.ts: /tests/ ✅ (94% coverage)
├── 📝 API docs: /docs/auth.md ✅
└── Coverage: 100%
Integrity:
├── Single Status: ✅ (only in Completed)
├── Artifacts Match: ✅ (all deliverables present)
├── No Duplicates: ✅ (removed from Active)
└── Audit Logged: ✅ (change documented)
Status: ✅ Verified
After completing this skill, write to .sessions/SESSION_[date]-[name].md:
### [HH:MM] Close-Task 150 Complete
**Task:** <task updated>
**New Status:** <status>
**Reason:** <transition reason>
**Artifacts:** <verified deliverables>
Remember: Task tracking isn't bureaucracy — it's clarity. One status, one location, artifacts that prove completion. When everyone knows the real state, work flows smoothly.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.