Compact the session into gitignored `.codeconductor/sessions/handoff.md` (redact secrets).
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-handoff. The user request follows the skill mention.
Handoff request: $ARGUMENTS
Command: handoff (fixed for this workflow — do not infer from user text)
npx cc-codeconductor ccep profile handoff --output json to get the phases and their roles.npx cc-codeconductor ccep compile --command handoff --phase <phase-id> "$ARGUMENTS" --view prompt --output jsonnpx cc-codeconductor ccep evaluate --command handoff --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.Invoke docs. Write only .codeconductor/sessions/handoff.md (gitignored).
Do not write .codeconductor/handoff.md or any tracked path.
Before writing, redact secrets, tokens, API keys, passwords, connection strings,
.env contents, and log/stack-trace lines that embed those values. Summarize
errors instead of pasting dumps. If unresolved credential material remains, stop
and wait for a human (CCEP stopOnHighRisk).
Include: goal, Task Card status (no secret fields), files touched, test
pass/fail (not log dumps), open questions, the next $cc- command, plus links
to the Delivery Ledger and verification evidence when they exist. Do not repeat
the original request or transcript.
If a Delivery Ledger exists, run npx cc-codeconductor odd handoff --id <ledger-id> --output json
and use its handoff envelope as the source for these fields. Secret redaction
still applies.
Do not edit source or tests.
Report the handoff path. Another session should be able to continue from that file alone.
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.