From idh
Create a ticket as a handoff document with required sections for TDD workflow.
npx claudepluginhub minhhaduong/imperialdragonharnessThis skill uses the workspace's default tool permissions.
`[Imagine → Plan]`
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
[Imagine → Plan]
Tickets are handoff documents. A new agent will only have the context provided.
## Context
What problem or need this addresses. Why now.
## Relevant files
- `path/to/file.py` — role in this task
## Actions
1. Concrete step
2. Concrete step
## Test
- What test to write first (red step of TDD)
## Verification
- [ ] How to confirm each action worked
## Invariants
- What must not break (tests, build, existing behavior)
## Exit criteria
- Definition of done — when is this ticket complete?
Create the ticket using whatever system the project has (git-erg tickets/ directory preferred, forge issues as fallback). The agent knows how to use the available tools.
When investigation spawns sub-tickets:
/celebrate step 7).