OpenSpec integrieren (spec-driven Workflow fuer Claude Code)
openspec init --tools claude --language de: Slash-Commands /opsx:* (propose, apply, archive, explore, sync, update) und zugehoerige Skills unter .claude/, Konfiguration in openspec/config.yaml (Artefakte auf Deutsch, Schema spec-driven). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
28
openspec/config.yaml
Normal file
28
openspec/config.yaml
Normal file
@@ -0,0 +1,28 @@
|
||||
schema: spec-driven
|
||||
|
||||
context: |
|
||||
Language: de
|
||||
All artifacts must be written in de.
|
||||
Keep OpenSpec structural headings and SHALL/MUST keywords in English.
|
||||
|
||||
# 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
|
||||
|
||||
# Per-operation guidance (optional)
|
||||
# Add advisory guidance for how apply and archive work should be conducted.
|
||||
# This is separate from artifact rules above.
|
||||
# Example:
|
||||
# operations:
|
||||
# apply:
|
||||
# guidance:
|
||||
# - Keep test summaries concise
|
||||
# archive:
|
||||
# guidance:
|
||||
# - Summarize the archive outcome before finishing
|
||||
Reference in New Issue
Block a user