From csdlc
Package completed work for human review (CSDLC Step 6). Summarize what shipped, link PRs, flag judgment calls. Optimized for async review. Use when the user says "present", "show me what shipped", "package this", "ready for review", or after /qa passes.
npx claudepluginhub danhannah94/claymore-plugins --plugin csdlcThis skill uses the workspace's default tool permissions.
Package this for review: **$ARGUMENTS**
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Package this for review: $ARGUMENTS
Step 6 is where the human reviews with fresh eyes. This skill packages the work into a format optimized for async review — the user may not be at the same machine where the work was done. The presentation needs to be scannable, complete, and honest about what needs human judgment.
Gather the deliverables. Collect for the specified scope:
/review (Step 4)/qa (Step 5)Produce the presentation.
## Ready for Review: {Epic or Story ID}
### Summary
{2-3 sentences: what was built, why, and the overall result}
### What Shipped
| Story | Title | PR | Tests | Status |
|-------|-------|-----|-------|--------|
| {ID} | {title} | [#{num}]({url}) | {pass/fail} | Ready |
### Changes at a Glance
- {N} files changed across {M} PRs
- {X} new tests added
- {Y} lines added, {Z} removed
### Needs Your Judgment
These items passed QA but need human eyes:
- {UX decision or aesthetic call}
- {Edge case where "correct" is debatable}
- {Anything that feels off but isn't technically wrong}
### Known Limitations
- {What this doesn't handle yet}
- {Tech debt introduced}
### Process Notes
- {Anything unusual about how this was built}
- {Lessons learned during implementation}
Write to Foundry. Post the presentation as a review on the epic doc in Foundry using submit_review. This makes it visible to anyone reading the project docs.
Report to the user. Surface the presentation in the conversation. End with: