config.yaml 922 B

1234567891011121314151617181920212223242526272829303132
  1. schema: spec-driven
  2. # Project context (optional)
  3. # This is shown to AI when creating artifacts.
  4. # Add your tech stack, conventions, style guides, domain knowledge, etc.
  5. # Example:
  6. # context: |
  7. # Tech stack: TypeScript, React, Node.js
  8. # We use conventional commits
  9. # Domain: e-commerce platform
  10. # Per-artifact rules (optional)
  11. # Add custom rules for specific artifacts.
  12. # Example:
  13. # rules:
  14. # proposal:
  15. # - Keep proposals under 500 words
  16. # - Always include a "Non-goals" section
  17. # tasks:
  18. # - Break tasks into chunks of max 2 hours
  19. # Per-operation guidance (optional)
  20. # Add advisory guidance for how apply and archive work should be conducted.
  21. # This is separate from artifact rules above.
  22. # Example:
  23. # operations:
  24. # apply:
  25. # guidance:
  26. # - Keep test summaries concise
  27. # archive:
  28. # guidance:
  29. # - Summarize the archive outcome before finishing