seis-product

Define the user, job, product surface, and expected outcome first, then convert the intent into a bounded slice with acceptance criteria. The Skill provides a product slice template covering outcome, target user, workflow, validation evidence, rollout, risks, and next steps.

A product slice should include outcome, target user, primary workflow, acceptance criteria, affected surfaces, validation evidence, rollout and rollback plans, risks and non-goals, and the next implementation step. This structure keeps planning bounded and reviewable.

Tie every product claim to concrete evidence such as validation commands, screenshots, tests, docs, or generated reports. Do not claim release readiness without validation and CI evidence supporting it.

Avoid using it to turn vague ideas into broad rewrites or to produce marketing-only artifacts like landing pages when the work needs a usable app, tool, dashboard, or workflow surface. Keep slices bounded and tied to real product surfaces.

Each slice is mapped to SEIS lanes: governance, cloud, code, design, data, security, automation, research, and docs. This ensures roadmap decisions stay source-controlled and aligned with long-term direction.