Run the API contract workflow for public interface changes, compatibility constraints, contract tests, documentation, and review.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Invoke as $cc-api-contract. The user request follows the skill mention.
API contract request: $ARGUMENTS
Command: api-contract (fixed for this workflow — do not infer from user text)
npx cc-codeconductor ccep profile api-contract --output json to get the phases and their roles.npx cc-codeconductor ccep compile --command api-contract --phase <phase-id> "$ARGUMENTS" --view prompt --output jsonnpx cc-codeconductor ccep evaluate --command api-contract --input <planner.json> --output json. If stop is true, show questions or risks and wait for human input.prompt for its phase — never forward raw $ARGUMENTS to planners.If openspec status reports an active change folder:
npx cc-codeconductor openspec validate --output jsonnpx cc-codeconductor openspec analyze --output jsonstop is true or any finding is CRITICAL, stop. Do not delegate to implementer.$cc-api-contractRun the CLI as npx cc-codeconductor <same argv>.
Adopt the task-coach role as defined in AGENTS.md.
The Task Card must classify the task as high risk by default and include the affected public interface, request/response examples, compatibility notes, versioning impact, consumer impact, contract tests, and docs acceptance criteria.
STOP here. Show the completed Task Card and wait for human confirmation.
Adopt the architect role as defined in AGENTS.md.
Define the API contract, validation strategy, compatibility behavior, docs or OpenAPI changes, and reviewer blocking conditions.
STOP here. Show the Technical Plan and wait for explicit human approval.
Adopt the implementer role as defined in AGENTS.md.
Apply the minimal diff, preserve compatible behavior unless explicitly approved as breaking, and update only the planned files.
Adopt the tester role as defined in AGENTS.md.
Add or update tests for request shape, response shape, status/error behavior, and backward compatibility.
Adopt the reviewer role as defined in AGENTS.md.
Block on missing contract tests, undocumented breaking changes, or docs/OpenAPI drift.
Run $cc-review on the diff before merging.
No 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.