feature

Preventing scope creep during cross-platform feature development requires automated governance systems with mandatory checkpoints. This skill enforces a three-gate approval system to verify core requirements before progressing through planning, implementation, and integration phases.

A gated workflow for cross-platform feature delivery uses mandatory checkpoints to validate scope and stakeholder approval before moving forward. It coordinates web and iOS implementation through a playground-first approach with explicit compilation verification.

Enforcing stakeholder approval checkpoints for web and iOS features requires explicit user validation gates at each stage. This skill mandates three user approval checkpoints to ensure cross-functional teams validate requirements before playground implementation and final integration.

Playground-first development works with cross-functional teams by establishing an isolated testing environment before integration. It coordinates web and iOS platforms while requiring compilation verification to ensure exact adherence to original feature requests.

To start a gated feature workflow, use the /feature command followed by your feature description. This initiates the playground-first workflow, triggering the three-gate system to govern planning, testing, and approval stages.