Files
claude-engineering-plugin/plugins/compound-engineering/skills/jira-ticket-writer/references/api_reference.md
John Lamb bf1f79aba4 Merge upstream origin/main (v2.60.0) with fork customizations preserved
Incorporates 78 upstream commits while preserving all local fork intent:
- Keep deleted: dhh-rails, kieran-rails, dspy-ruby, andrew-kane-gem-writer (FastAPI pivot)
- Merge both: ce-review (zip-agent-validator + design-conformance-reviewer wiring),
  kieran-python-reviewer (upstream pipeline + FastAPI conventions),
  ce-brainstorm/ce-plan/ce-work (upstream improvements + deploy wiring checks),
  todo-create (upstream template refs + assessment block),
  best-practices-researcher (upstream rename + FastAPI refs)
- Accept remote: 142 remote-only files, plugin.json, README.md
- Keep local: 71 local-only files (custom agents, skills, commands, voice)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-31 12:27:52 -05:00

969 B

Reference Documentation for Jira Ticket Writer

This is a placeholder for detailed reference documentation. Replace with actual reference content or delete if not needed.

Example real reference docs from other skills:

  • product-management/references/communication.md - Comprehensive guide for status updates
  • product-management/references/context_building.md - Deep-dive on gathering context
  • bigquery/references/ - API references and query examples

When Reference Docs Are Useful

Reference docs are ideal for:

  • Comprehensive API documentation
  • Detailed workflow guides
  • Complex multi-step processes
  • Information too lengthy for main SKILL.md
  • Content that's only needed for specific use cases

Structure Suggestions

API Reference Example

  • Overview
  • Authentication
  • Endpoints with examples
  • Error codes
  • Rate limits

Workflow Guide Example

  • Prerequisites
  • Step-by-step instructions
  • Common patterns
  • Troubleshooting
  • Best practices