Track Management
Organize and track software work with structured methodology
Software teams struggle with unclear work boundaries and lost context. Track Management provides a structured system for organizing work into spec-driven, phased tracks with clear progress visibility.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「Track Management」を使用しています。 Create a feature track for user authentication
期待される結果:
Generated track user-auth_20250225 with spec.md defining 5 functional requirements, 3 non-functional requirements, and acceptance criteria. Plan includes 3 phases: Foundation (data models, migrations), Core Logic (auth flow, validation), and Integration (UI, end-to-end tests).
「Track Management」を使用しています。 Update progress on bug fix track
期待される結果:
Track fix-login-error_20250220 updated: Phase 1 (Reproduction) complete with commit a1b2c3d, Phase 2 (Fix) in progress, 2 of 8 tasks completed. No blockers identified.
セキュリティ監査
安全All static analysis findings are false positives. The skill consists entirely of markdown documentation files with no executable code. Detected patterns (backticks, SHA references) are markdown formatting and documentation examples, not actual security risks.
品質スコア
作れるもの
Feature Development Tracking
Break down new features into tracked work units with clear specifications, phased implementation plans, and verifiable acceptance criteria.
Bug Fix Documentation
Document bug reproduction, track fix implementation through phases, and maintain verification records for quality assurance.
Technical Debt Management
Plan and execute refactoring work with clear scope boundaries, risk assessment, and rollback checkpoints.
これらのプロンプトを試す
Create a new feature track for [feature name]. Gather requirements, define acceptance criteria, and generate a spec.md with functional and non-functional requirements.
Based on the spec.md for [track name], create a phased implementation plan with atomic tasks, verification steps, and estimated effort for each phase.
Update the track status for [track name]. Mark completed tasks with commit SHAs, update phase progress, and identify any blockers or dependencies.
Revert track [track name] to phase [N]. Identify all commits to revert, update status markers, and document the revert reason in the track registry.
ベストプラクティス
- Keep tracks focused on a single logical change that can complete in 1-5 days
- Include verification tasks after each phase before proceeding
- Record commit SHAs for all completed tasks to enable traceability and rollback
回避
- Creating tracks that are too large with multiple unrelated features
- Skipping verification tasks to move faster
- Not updating status markers immediately after completing work