Guides agents through authoring BACKLOG.md and OpenSpec change folders. Use when running /cc-backlog or /cc:backlog, creating or appending backlog items, or preparing work for /cc-openspec. Delivery is skill openspec.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Create or append BACKLOG.md, then openspec validate / plan. Do not deliver
the item here.
/cc-backlog, first backlog in a repo, or appending ### BC-xxx itemsNOT for executing an item (openspec) or for scorecards (evaluation).
graphify-out/graph.json exists, graphify query "<objectives>". Then
repo-explorer. Scope names real files.task-coach. One grilling question per assumption. Reject vague
acceptance ("improve UX"). At most 3 [NEEDS CLARIFICATION].ccep evaluate --command backlog. If stop, wait for the human.BACKLOG.md from presets/templates/BACKLOG.md or append under
## Items. Do not rewrite ## Global or ## Archive.BC-013).npx cc-codeconductor openspec validate. Fix until valid.openspec plan BC-xxx for each new item this run. Then tell the user
to run /cc-openspec.Required sections: ## Global, ## Items, ## Archive. Each item:
### BC-001 | Title with Priority, Status (READY after grilling), Type,
Depends on, Description, Scope, Out of scope, Acceptance.
Local artifacts (BACKLOG.md, openspec/, .codeconductor/openspec-state.json)
are gitignored in consumer projects. Do not git add them.
| Rationalization | Reality |
|---|---|
| This fix is small; skip the Task Card | Every item needs measurable acceptance. |
| I'll validate later | Do not plan until openspec validate passes. |
| Archive can be rewritten | Archive is history. Never rewrite or re-execute. |
openspec-state.json by handopenspec validate exit 0FR/SC-ready measurable acceptance/cc-openspec for deliveryNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding monitoring, metrics, logging, or tracing to Spring AI or LLM integration code. Covers token tracking, latency measurement, cost estimation, and prompt/response logging. Use when user mentions AI monitoring, token costs, or LLM observability.
The English summary is being prepared. Showing the original description.
Provides expert knowledge for building modern native Android apps using Kotlin, Jetpack Compose, Material Design 3, MVI architecture, Hilt dependency injection, and Media3/ExoPlayer.
The English summary is being prepared. Showing the original description.
Design, implement, review, and audit Android Jetpack Compose UI/UX for phone interfaces. Use when a request concerns concrete Compose layout, components, interaction, accessibility, or visual behavior. Do not activate for framework or dependency presence alone; non-UI Android work is excluded.
The English summary is being prepared. Showing the original description.
Provides expert knowledge for designing, implementing, and managing REST API versioning strategies with deprecation workflows.
The English summary is being prepared. Showing the original description.
Provides expert knowledge for building Astro 5+ sites with Islands Architecture, Content Collections, TypeScript, and performance-first rendering strategies.
The English summary is being prepared. Showing the original description.
Audits token storage mechanisms to prevent XSS-based JWT theft.
The English summary is being prepared. Showing the original description.