feature — spec → plan → build, effort-scaled

/feature <description> — start (or resume) a piece of work /feature — list changes in flight under out/dev/

Answer one question: what is the smallest process that gets THIS change built correctly? The two documented failure modes of workflow suites are opposite: heavyweight gates firing on typo-sized changes, and freestyle sessions shipping unverified scope creep. This skill scales the process to the change — never the other way around.