solo-deliverable-management

What problem does it solve? Solo developers and small teams often lose track of project documents because files are scattered, inconsistently named, and lack clear versioning or review standards. This Skill enforces a unified workspace structure, naming convention, and promotion process so every deliverable stays organized and traceable. ## Core Features & Use Cases - Standardized Workspace Structure: Organizes documents into numbered folders from 00_관리 (management) through 06_산출물 (final deliverables), covering requirements, planning, design, UI, QA, and releases. - Naming & Semantic Versioning Rules: Applies the {type}_{topic}_v{version} naming pattern with clear version semantics (v0.x drafts, v1.0 approved, v2.0 major rewrites). - v1.0 Quality Gate: Runs type-specific checklists (feature specs, architecture, wireframes, QA scenarios) through PL self-review, cross-verification, and PM final approval before promotion. - Use Case: When you finish drafting a payment feature spec, ask to promote it to v1.0 and the Skill walks through the full checklist, updates the file header, and logs the decision in decision_log.md. ## Quick Start Ask the assistant to list all current deliverables and their versions, or request to promote a specific document to v1.0 using the quality gate checklist.