forgejo-mcp/openspec/config.yaml
Christoph Görn 4eff5ffaf8 chore: 🚀 add OpenSpec workflow, beads issue tracker, and merge PR proposal
- Add OpenSpec artifact-driven workflow (.claude/commands/opsx/, .claude/skills/openspec-*)
- Add beads git-backed issue tracker (.beads/)
- Add git hooks for workflow automation (.husky/)
- Add "Landing the Plane" session completion workflow to AGENTS.md
- Create merge-pull-request proposal (openspec/changes/merge-pull-request/)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-30 08:25:11 +01:00

20 lines
573 B
YAML

schema: spec-driven
# Project context (optional)
# This is shown to AI when creating artifacts.
# Add your tech stack, conventions, style guides, domain knowledge, etc.
# Example:
# context: |
# Tech stack: TypeScript, React, Node.js
# We use conventional commits
# Domain: e-commerce platform
# Per-artifact rules (optional)
# Add custom rules for specific artifacts.
# Example:
# rules:
# proposal:
# - Keep proposals under 500 words
# - Always include a "Non-goals" section
# tasks:
# - Break tasks into chunks of max 2 hours