build-feature
Design in Spec mode, build, and verify with prove-it-works. Use for features, prototypes, and visual parity; use Spec mode alone for plans, or refactoring-playbook for large refactors, migrations, and dependency upgrades.
Cynnamoroll · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Cynnamoroll/factory-stack --skill build-featureAbout this skill
name: build-feature description: "Design in Spec mode, build, and verify with prove-it-works. Use for features, prototypes, and visual parity; use Spec mode alone for plans, or refactoring-playbook for large refactors, migrations, and dependency upgrades." license: MIT compatibility: droid
Build feature
Own the design and review. Delegate implementation.
1. Ground and design
- Run
explain-howon the affected subsystem. - Enter Spec mode. Write the caller's view first (the call sites or user steps), then the data shape and its organizing structure (
engineering-principles, model-the-domain), then the plan. Screen the shape against references/design-red-flags.md. For a contested or cross-cutting design, write the rationale with references/rationale-template.md. Exit Spec mode for approval. - If the shape has several valid forms and the choice matters, run
/race-worktreesinstead of picking one by feel.
2. Plan the work
Write four todo items, marking any inapplicable item n/a: <reason>.
- Blocking first steps. What must land before anything else.
- Independent workstreams. Disjoint files or layers that can run in parallel.
- Shared state. Split shared write targets. Serialize only real invariants.
- Smallest decomposition. If one worker is best, say why.
3. Build
Give each workstream to one principled-worker Task with file paths, data shape, and success criteria. Parallel writers on separate files use droid exec -m auto --auto medium --worktree <name>. Review every diff. Verify each small, ordered commit before the next.
4. Verify
Run prove-it-works on the running app. If the design was contested, run adversarial-review before shipping.
Variants
- Prototype. The deliverable is a decision, not code. Build throwaway variants in a scratch directory outside the source tree, behind one switcher (buttons or a key), using the lightest stack that shows the idea. Observe each variant (screenshots with
agent-browser, or logged timing). Present the variants, evidence, and a recommendation, and say plainly that the prototype is throwaway. - Visual parity. Capture a screenshot baseline of every component state before any change. Never edit the baseline or the harness to pass. Migrate one component at a time, shared pieces first. A component passes only at zero image diff against its baseline.
When validation fails
Fix the cause and rerun prove-it-works. If the design itself is wrong, go back to Spec mode rather than patching around it.
Done when
The reply covers what was built, the design choices and why, the four planning items, the prove-it-works evidence, and open decisions. A prototype reply has the variants, evidence, recommendation, and scratch path. A visual-parity reply has each component's diff result.