develop-feature-sliceslisted

Plan, implement, test, review, and commit one observable feature slice at a time after requirements, experience, technical solution, and environment outcomes are accepted. Use when production development is authorized, when a large feature needs decomposition, when resuming an active slice, or when user corrections must be distilled into durable regression rules. Require human slice acceptance by default, provide self-check steps, preserve unrelated Git work, and create focused functional commits.
railgun20001/the-first · ★ 0 · Code & Development · score 72

Install: claude install-skill railgun20001/the-first

# Develop Feature Slices Deliver small, complete user outcomes instead of large batches of plausible but unverified code. ## Verify readiness Before planning or editing: 1. Read project instructions, `THE-FIRST.md`, accepted requirements, experience decisions, technical solution, environment outcome, and feedback rules relevant to the scope. 2. Confirm the project is in `development` and the required phase gates are accepted. Do not treat a plan or prototype as production authorization. 3. Inspect Git branch, HEAD, working tree, staged changes, relevant history, and repository conventions. 4. Trace the real implementation path, existing components, dependencies, schemas, callers, tests, build, and runtime boundaries. 5. Identify unrelated user or concurrent changes and keep them out of the slice. If the project is not a Git repository, explain that focused feature commits are unavailable and request permission before initializing Git. If permission is declined, continue only if the user accepts that limitation and record it. ## Define vertical feature slices Split accepted scope into the smallest slices that each deliver an observable user or system outcome across the necessary layers. Do not split only by technical layer when that leaves nothing meaningful to review. For each slice, define: - A stable slice ID and title. - Requirement and source-of-truth links. - Observable result and target user. - Included and explicitly excluded behavior. - Interface, data, visua