← ClaudeAtlas

development-workflowlisted

Spec-driven development lifecycle — EARS requirements, technical design docs, implementation tracking, and contribution guidelines. Use when planning features, defining requirements, or managing project lifecycle.
bg-szy/TOP-SKILLS · ★ 1 · AI & Automation · score 70
Install: claude install-skill bg-szy/TOP-SKILLS
# Development Workflow Structured approach to software development ensuring requirements are clearly defined, designs are meticulously planned, and implementations are thoroughly documented with proper contribution practices. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. **Project Planning & Requirements:** - Starting new features or phases of work - Defining requirements using structured notation - Creating technical designs and architecture documents - Managing implementation plans from concept to completion - Ensuring thorough documentation before coding - Understanding project structure and existing patterns **Repository Contributions:** - Creating issues, commits, or pull requests in a repository - Needing to follow repository guidelines before making contributions - Creating PRs, pushing code, or following contribution workflows - Following project-specific contribution guidelines **Quality Assurance:** - Ensuring two-stage review (spec compliance first, then code quality) standards are met - Validating tests and requirements before implementation - Managing project decisions and trade-offs documentation - Tracking progress and blockers ## Part 1: Spec-Driven Development ### Core Artifacts Maintain these artifacts throughout the project lifecycle: | Artifact | Purpose | Location | |--------