Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/project-context
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?