project-context
Defines the overall project purpose, operating model, and roles for Hackathon II – Todo Spec-Driven Development. Always load for any project-related task.
When & Why to Use This Skill
This Claude skill establishes a comprehensive project framework for Spec-Driven Development (SDD). It defines the core operating model, project purpose, and specific roles for human-AI collaboration, ensuring all development tasks adhere to a 'spec-first' methodology and cloud-native principles. By providing a clear project context, it minimizes improvisation and maximizes architectural consistency.
Use Cases
- Establishing a 'spec-first' development environment where Claude acts as the primary implementer and the human acts as the system architect.
- Enforcing standardized operating models and core principles during hackathons or rapid prototyping phases to ensure deterministic outcomes.
- Defining clear boundaries and roles between humans and AI agents to streamline the software development lifecycle (SDLC) without manual code intervention.
- Ensuring all project-related outputs follow a structured Markdown format with clear rationale and phase-aligned steps.
| name | project-context |
|---|---|
| description | Defines the overall project purpose, operating model, and roles for Hackathon II – Todo Spec-Driven Development. Always load for any project-related task. |
Project Context – Hackathon II
Project Overview
This project is part of Hackathon II: Todo Spec-Driven Development.
The objective is to evolve a Todo system through multiple phases using:
- Spec-Driven Development (SDD)
- AI-assisted implementation via Claude Code
- Cloud-native and agent-based architecture
Operating Model
- All development is spec-first
- Humans design and refine specifications
- Claude generates implementations
- No manual code writing is allowed
Roles
- Human: System Architect, Spec Author, Reviewer
- Claude: Implementer, Analyzer, Validator
Core Principles
- Determinism over improvisation
- Clarity over speed
- Reusable intelligence over one-off solutions
Output Expectations
- Structured Markdown
- Clear steps and rationale
- Phase-aligned outputs
- No assumptions without specs