feature-design

Phase 4: turn validated needs into a minimal, coherent capability and user journey before implementation planning.

SKILL.md

GitHub
<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

feature-design

This skill is part of Misbah Khursheed's Build Like This workflow. Thinking, evidence, and explicit trade-offs come before generated output.

Project identity and sources of truth

The repository where this skill is installed is the host project being built. Build Like This is the method used to build it; mstack only installs and reconciles method resources. Do not assume mstack or Build Like This is the product unless project-owned sources explicitly identify this repository as mstack itself.

Use project-owned docs/, decisions, executable code, and tests as sources of truth. .mstack/templates/ are reference scaffolds to copy and adapt into project-owned documents, not product requirements and not a replacement for docs/.

Purpose

Choose and design the smallest product capability likely to improve a validated need. This establishes product behavior and interaction intent; feature-planning later turns an agreed capability into implementation-ready slices.

Required inputs

  • Validated users, prioritized needs, evidence/assumptions, desired outcome, constraints, and non-goals.
  • Existing product behavior, design system/platform patterns, accessibility target, and relevant technical constraints.
  • Actor/permission implications, sensitive-data concerns, operational limits, and success measures.

If a missing input would materially change the result, state the gap and obtain or discover it before proceeding. Otherwise label the assumption and continue.

Process

  1. Have the product manager lead; delegate alternative journey design to the product designer and feasibility/risk review to relevant engineering or security specialists.
  2. Define the user outcome and evaluation criteria before generating alternative capabilities or flows.
  3. Compare alternatives by need fit, behavior change, complexity, accessibility, risk, reversibility, and learning value.
  4. Select the narrowest coherent end-to-end journey and specify success, loading, empty, validation, denial, degraded, failure, and recovery states.
  5. Identify actor/permission, data, contract, security, content, instrumentation, and operational questions without inventing implementation.
  6. Prototype and test the riskiest interaction or assumption at the lowest useful fidelity, then document the selected behavior and non-goals.

Output contract

  • A selected capability and alternative rationale mapped to validated needs and measurable outcome.
  • A complete journey/state design with actor, accessibility, failure/recovery, content, and contract questions.
  • Behavioral acceptance criteria, prototype/evidence results, non-goals, and implementation-planning handoff.

Guardrails

  • Do not treat a polished screen or common pattern as evidence of need fit.
  • Do not make interface checks the source of truth for authorization or business invariants.
  • Do not expand the first slice with speculative personalization, platform work, or adjacent personas.

Delegation and parallel safety

  • Material lifecycle work must delegate at least one bounded specialist lane when subagents are available. Prefer two or more concurrent lanes only for independent evidence gathering, analysis, or non-overlapping file ownership.
  • The active lead owns integration and acceptance. Supporting agents do not recursively delegate unless explicitly promoted to lead a named lane.
  • Assign distinct outputs and ownership. Serialize shared docs, contracts, schemas, migrations, deployments, external writes, and overlapping file edits.
  • When subagents are unavailable, perform the same named specialist passes sequentially and state that constraint instead of implying parallel verification.
  • Delegation never grants permission for outreach, consequential external actions, destructive changes, paid resources, or production operations.

End with the evidence gathered, verification performed, and any residual risk or unresolved decision.