What problem does it solve? Teams lose track of where work stands and accumulate misnamed or stale documentation when specs, plans, and feature docs lack a consistent flow. This Skill defines how work moves from roadmap through feature, spec, plan, and implementation, and how to classify each piece of work so it earns the right durable artifact. ## Core Features & Use Cases - Five-layer workflow spine: Routes work through Roadmap → Feature → Spec → Plan → Implement, with entry points like /spec, /plan, /implement-step, and /retrofit for changes that skipped the flow. - Work-type classification: Classifies work as new-capability, change-to an existing capability, or fix-infra, deciding whether a feature doc is created, updated, or skipped entirely. - Artifact lifecycle layout: Defines where artifacts live — evergreen capability docs in _features/, temporal increment bundles in _work/<slug>/, and durable runbooks in docs/. - Use Case: Before writing a spec for a new article-card placeholder behavior, consult this Skill to learn it is a change to the existing article-card capability doc rather than a new feature doc, keeping the capability catalog clean. ## Quick Start Ask the assistant to consult the workflow skill to classify a planned change and determine which feature doc or artifact it should produce.
