runtsang/RebuttalStudio / skills/stage5/final-remarks
stage5-final-remarks
VerifiedFill a Stage5 final remarks template using condensed discussion markdown from all reviewers and optional rating changes. Use when generating final remarks after Stage3/Stage4 discussion.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
| references/run-template.md | markdown | 626 B |
SKILL.md
View on GitHub---
name: stage5-final-remarks
description: Fill a Stage5 final remarks template using condensed discussion markdown from all reviewers and optional rating changes. Use when generating final remarks after Stage3/Stage4 discussion.
---
# Stage5 Final Remarks Skill
## Goal
Generate a complete Stage5 final remarks markdown by filling template placeholders from multi-reviewer evidence.
## Inputs
- `template_markdown`: placeholder-based template source.
- `reviewer_summaries`: array of reviewer records, each containing:
- `reviewerId`
- `condensedMarkdown`
- `originalRating` (optional)
- `finalRating` (optional)
If `template_markdown` is empty, use [references/run-template.md](references/run-template.md).
## Output
Return strict JSON:
```json
{ "filledMarkdown": "..." }
```
## Rules
1. Preserve the template structure and section order.
2. Replace placeholders with grounded content from `reviewer_summaries` only.
3. Keep uncertain or missing items concise; do not fabricate numbers, dates, quotes, or experiments.
4. Keep tone respectful, concise, and rebuttal-ready.
5. Generate `{{key_strengths_points_markdown}}` as a concise markdown bullet list with 4-5 items summarized across reviewers.
6. Generate valid markdown table rows for `{{concern_rows_markdown}}`.
7. When rating updates are provided, reflect only explicit score transitions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |