time-resource-estimator
Estimate realistic project timelines, break down hours by feature/phase, include buffer for revisions, set achievable client expectations, and avoid over-promising deadlines you can't meet.
Estimate realistic project timelines, break down hours by feature/phase, include buffer for revisions, set achievable client expectations, and avoid over-promising deadlines you can't meet.
Validates skills against production-level criteria with 9-category scoring. This skill should be used when reviewing, auditing, or improving skills to ensure quality standards. Evaluates structure, content, user interaction, documentation, domain standards, technical robustness, maintainability, zero-shot implementation, and reusability. Returns actionable validation report with scores and improvement recommendations.
Session state and context handoff management with SESSION.md tracking. Use for multi-session projects, resuming after context clear, phase tracking, or encountering handoff protocol, session recovery, phase progress, checkpoint errors.
Guide Spec-Driven Development (SDD) workflow for planning changes before implementation. Use when: creating specs, proposals, planning features, using OpenSpec or similar tools. Keywords: spec, specification, SDD, proposal, openspec, design doc, 規格, 提案, 設計文件.
Manage and guide developers through active development methodology workflows. Use when: TDD, BDD, SDD, ATDD, or custom methodology workflows are needed. Keywords: methodology, workflow, TDD, BDD, SDD, ATDD, phase, checkpoint, development process.
引導規格驅動開發 (SDD) 工作流程,在實作前規劃變更。 使用時機:建立規格、提案、規劃功能、使用 OpenSpec 或類似工具。 關鍵字:spec, specification, SDD, proposal, openspec, design doc, 規格, 提案, 設計文件。
Event Storming 기법을 사용하여 PlantUML 시퀀스 다이어그램을 작성하고 유저스토리 개발을 준비합니다. 기획 구체화 시 사용하세요.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
USE WHEN: returning to a project after time away (1 day to 30 days), needing project status briefing, understanding where work left off, determining next steps. DO NOT USE WHEN: actively working on a known task, not in a git repository, or when specific file/code questions are asked.
Agile/Scrum süreçleri, backlog yönetimi ve paydaş iletişimi.
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
Save a work checkpoint to preserve context for multi-session projects. Use when pausing work on a feature, completing a milestone, or before ending a session.
This skill should be used when creating or updating PROJECT.md files, planning sprints, defining project goals, or managing project scope. It provides templates and best practices for PROJECT.md-first development.
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Implementation roadmap, timeline oluşturma, risk yönetimi ve kaynak planlaması rehberi.