Creates or updates feature implementation plan documents in doc/plan. Use when planning a new software feature, refining feature scope/name, tracking TODO/DONE progress, or marking a plan as achieved.
Determines project type from context to configure analysis thresholds. Checks prompt, scans documents, or asks user if type cannot be inferred. Outputs project_type for use by python-plan-optimization skill.
skill__spec__set `spec set <yyyy-mm-dd> <taskName>` [SET] Switch to existing CODE_SPEC.
Creates structured implementation plans from feature requirements. Use when planning new features, multi-phase projects, or when the user asks for an implementation plan, build plan, or development roadmap.
Use when determining how fast or slow motion should be—pacing action sequences, dramatic pauses, comedic beats, or any situation where the duration of movement matters.
Systematic todo management approach. Analyze task clarity before adding; ask for details when needed to ensure actionability. Uses Obsidian's todo.md with three regions: Important (重要), Todo, Finish (完成). Trigger when user says "添加任务", "新任务", "记录待办", "管理任务" or needs task reasoning, priority judgment, or task breakdown.
Use when executing implementation plans with independent tasks in the current session
Project organization, multi-agent coordination, bug reporting, feature requests, and documentation practices. Use when managing projects, coordinating work, or organizing development workflows.
프로젝트별 Claude Code 세션 시간을 집계하여 리포트 생성. 일별/주별/월별 시간 분포를 Obsidian 테이블로 시각화. "시간 추적", "프로젝트 시간", "time tracking" 등의 요청 시 자동 적용.
Use this skill when proposing new features or changes via the Spec PR process. Manages the creation, refinement, and approval of feature specifications before any code is written. Triggers include "create spec", "propose change", "start spec PR", or beginning feature definition.
Spec-driven development methodology for ANY software project. USE WHEN developing features, fixing bugs, creating skills, or preparing releases. USE WHEN user mentions specs, testing, release process, change proposals, or deployment. Provides flexible spec tooling guidance but STRICT release discipline.
Guide for spike-driven development methodology. Use when starting new features, testing architecture patterns, integrating unfamiliar APIs/data sources, or validating technical feasibility before full implementation. Emphasizes TDD, real data validation, and risk reduction through minimal proofs-of-concept.
Manages file-based work items through a lightweight kanban system using folder-based state management. Handles backlog capture, design phase, active work, review, and archiving. Creates items in 00-backlog/, moves through 10-in-design/, 20-in-progress/, 30-in-review/, to 90-archive/. Applies templates and checklists at each stage. Zero-friction backlog entry, clear decision gates between stages.
Use when designing complex technical features requiring cross-team coordination, system architecture decisions, data model changes, API definitions, or when stakeholders need comprehensive technical documentation before implementation
Start-of-session skill. Runs session preflight and then selects next work.
Create a Linear issue. Use when user asks to create an issue, register a task, track work, or needs a ticket before starting development. Do NOT load for: implementation work, code review, deployment.
Manage project tasks. Create, list, update, and track dependencies of tasks.
Enterprise Skill for advanced development
Synchronize plans from a spec file. Reads the spec, generates or updates related plans, marks deprecated plans, and updates the spec's Milestones section. Use when user changes a spec and wants to regenerate plans.
