docs: update workflow documentation to reflect production status

[jeremyeder]

Summary

Updates all workflow documentation to accurately reflect the current production-ready state of the workflows repository.

Changes

Main README.md

• ✅ Mark all workflows (spec-kit, bugfix, template) as Production Ready
• ✅ Update repository references from Gkrumbach07/spec-kit-template to ambient-code/workflows
• ✅ Add Template Workflow to available workflows list
• ✅ Update workspace structure to show all three workflows
• ✅ Document future platform integration plans
• ✅ Update all support links and references

New: Workflow Development Guide

• ✅ Created WORKFLOW_DEVELOPMENT_GUIDE.md - comprehensive one-pager covering:
  • Quick start with template-workflow
  • Configuration guide (ambient.json)
  • Slash command creation
  • Platform agent usage patterns
  • Contributing workflow
  • Best practices and common patterns
  • Troubleshooting

Template Workflow README

• ✅ Updated agent usage documentation
• ✅ Clarified that platform agents (Amber, Parker, Stella, Ryan, Steve, Terry) are automatically available
• ✅ Noted that example agents are for illustration only
• ✅ Encouraged leveraging platform agents before creating custom ones

New: Spec Kit Workflow README

• ✅ Created comprehensive README documenting:
  • All slash commands and phases
  • Agent orchestration patterns
  • Directory structure
  • Artifacts and outputs
  • Best practices and troubleshooting

Key Documentation Improvements

1. Agent Strategy Clarity: Platform agents from platform/agents/ are automatically loaded in ACP sessions. Workflows should leverage these rather than duplicating agent definitions.

2. Production Status: All three workflows now explicitly marked as production-ready with clear feature lists.

3. Repository Ownership: Centralized on ambient-code/workflows org repo.

4. Developer Experience: New Workflow Development Guide provides clear path for creating custom workflows.

Testing

• All documentation files render correctly in markdown
• Links are valid and point to correct locations
• Workflow structure accurately reflects repository state
• Agent usage patterns clearly documented

Impact

• Makes it clear that workflows are production-ready
• Provides clear guidance for custom workflow development
• Documents platform agent integration patterns
• Prepares repository for official platform adoption

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

[jeremyeder]

Feedback:

This is not intended:
Agent Strategy Clarity: Platform agents from platform/agents/ are automatically loaded in ACP sessions. Workflows should leverage these rather than duplicating agent definitions.

I want workflows to be the "container" that teams use to encapsulate "bring your own" philosophy, including agents.