Files
claude-engineering-plugin/plugins/compound-engineering/skills/ce-jira-ticket-writer/references/api_reference.md
John Lamb 5d4377338e
Some checks failed
CI / pr-title (push) Has been cancelled
CI / test (push) Has been cancelled
Release PR / release-pr (push) Has been cancelled
Release PR / publish-cli (push) Has been cancelled
Merge step (c): converge to ce-* convention for agents and skills
Aligns local custom agents, skills, and modified shared agents with upstream's
flat ce-<name>.agent.md + ce-<skill>/ convention introduced in upstream v3.x.

Changes:
- Delete 9 upstream-renamed agents for locally-dropped agents (design/*, rails
  reviewers, ankane-readme-writer, data-migration-expert, performance-oracle,
  security-sentinel)
- Delete ce-dhh-rails-style skill (local dropped dhh-rails-style entirely)
- Move 5 custom agents to flat ce-<name>.agent.md paths:
  * python-package-readme-writer, design-conformance-reviewer,
    tiangolo-fastapi-reviewer, zip-agent-validator, lint
- Rename 12 custom skill directories with ce- prefix:
  * john-voice, jira-ticket-writer, hugo-blog-publisher, weekly-shipped,
    proof-push, ship-it, story-lens, sync-confluence, excalidraw-png-export,
    python-package-writer, fastapi-style, upstream-merge
- Port local Python/FastAPI edits into upstream's flat ce-best-practices-
  researcher.agent.md and ce-kieran-python-reviewer.agent.md
- Update frontmatter name: fields in all 17 renamed files to match new paths

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-24 12:53:31 -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