development

name	development
description	Workflow and guidelines for full-cycle software development — from requirements gathering and system design through deployment, monitoring, and iteration. Focuses on building and shipping working software that delivers user and business value. You MUST load this skill when building features or acting as an autonomous developer responsible for end-to-end product delivery.
license	MIT

development

A comprehensive workflow for delivering complete, usable software that solves real needs. Covers the entire product lifecycle: understanding user needs, designing solutions, building, deploying, monitoring, and iterating.

WHEN TO USE

• When developing end-to-end features that span multiple layers (frontend, backend, data).
• When responsible for the full lifecycle: requirements → design → build → deploy → maintain.
• When shipping software that must deliver user or business value, not just correct code.
• When coordinating across technical and product concerns to make architectural trade-offs.

WHEN NOT TO USE

• For implementing well-defined, isolated specs without system design concerns (use coding).
• For algorithmic or data-structure focused tasks without product context (use programming).
• For tasks that are purely about writing tests (use tdd) or debugging.

Anti-Patterns

• Requirements Bypass: Implementing without validating understanding of the user need.
• Operational Blindness: Delivering code that works locally but fails in production due to missing monitoring, logging, metrics, or deployment considerations.