skills.rest
surfingalien
surfingalienCOMMUNITY
Explore all skills by this author →
GitHub

ck-review

Reviews architecture docs, RFCs, and specs with principal engineer feedback.

1|Updated May 6, 2026
Search Tags:#architecture#code review#documentation#design review#rfc#principal engineer#technical feedback
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill ck-review-surfingalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck-review
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/ck-review
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill ck-review-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical documents often bury the decision, skip tradeoffs, or over-engineer solutions, and authors lack access to a senior IC who will give blunt, structured pushback before a review meeting. ## Core Features & Use Cases - Principal Engineer Persona Review: Simulates feedback from a senior individual contributor focused on clarity, systems thinking, and shipping velocity. - Structured Review Checklist: Evaluates executive summary, problem definition, solution alternatives, technical soundness, execution plan, and writing craft. - Prioritized Verdict Output: Delivers feedback ordered critical to nice-to-have, ending with a clear Ship it / Revise / Rethink verdict and 2-3 actionable next steps. - Use Case: Paste a draft architecture RFC and receive blunt questions about failure modes, scope creep, and the smallest shippable version before sending it to your team. ## Quick Start Ask the assistant to run ck-review on your attached design doc and return prioritized feedback with a final verdict.

Frequently Asked Questions about ck-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get senior engineer feedback on a design doc?▼

Submit your design doc, RFC, or architecture proposal to this skill and it returns structured feedback modeled on a principal engineer. The review covers framing, tradeoffs, failure modes, and shipping plan, ending with a clear verdict and next steps.

What types of documents can this skill review?▼

It reviews architecture docs, design documents, API or data model proposals, technical RFCs, specs, and complex system code reviews. It is not intended for pure business strategy or executive platform-level reviews.

How is ck-review different from a CTO-style review?▼

ck-review focuses on individual craft, system clarity, and shipping velocity from a senior IC perspective. A CTO-style review instead emphasizes platform strategy, org-level execution, and mobile-first thinking.

What feedback format does the review produce?▼

Feedback is organized by priority from critical to nice-to-have, using direct probing questions and concrete examples. It ends with a verdict of Ship it, Revise and resubmit, or Rethink the approach, plus 2-3 actionable next steps.

When should I not use a principal engineer review?▼

Avoid it for pure business strategy documents or executive-level platform decisions, which need different lenses. It is designed for engineering documents where technical soundness, scope, and incremental delivery are the core questions.

Related Skills

Explore More Software Engineering Skills→
sunny0826sunny0826
3

rfc-writer

Draft structured RFC documents from rough ideas or requirements.

Community
Advanced
wangcb8i8iwangcb8i8i

revise-markdown

Identify, resolve, and remove all embedded review comments in markdown documents.

Community
Intermediate
jaydubya818jaydubya818

document-review

Coordinate parallel persona reviews to surface issues in requirements or plan documents.

Community
Advanced
DavidROliverBADavidROliverBA
49

adr

Generate Architecture Decision Records with context, alternatives, and approvers.

Community
Advanced