Startup Feature Delivery and Release Review
Take features from scoped plan to release with engineering, design, QA, security, documentation, and rollout checks.
Before & after
Same prompt, same agent — the only difference is the skill.
Sure, I can review it. What's the feature about, and what are you most concerned about? Is this a customer-facing change or internal? I'd look for logical correctness, error handling, and whether it fits your architecture. Do you want me to check the design too, or just code? Are there any security considerations? QA testing coverage? Let me know the specifics and I can give you a thorough review before you ship.
GSTACK MULTI-LAYER REVIEW: FEATURE READY FOR SHIP
CEO LAYER → SCOPE & IMPACT
Feature scope → Matches sprint goal (✓)
Stakeholder alignment → Confirmed with marketing, support (✓)
Metrics → Tracked in analytics (✓)
Risk level → Low, feature flag in place (✓)
Ship go-no-go → GO, proceed to next layer
ENGINEERING LAYER → CODE QUALITY & PERF
Issues found → 2 blocking, 3 nice-to-have
BLOCKING:
1. Missing null check on user.preferences (line 47) → Crash risk
2. Database query N+1 pattern → 3x slower on 1k users
NICE-TO-HAVE:
3. Error message vague ("Failed") → Unclear to users
4. No deprecation warning on old endpoint
5. Type inference could be more specific
Performance → Worse than target by 12% on cold start
Code review → BLOCKED until null check + query optimization fixed
DESIGN LAYER → UX & ACCESSIBILITY
Issues found → 1 blocking, 2 minor
BLOCKING:
1. Button contrast ratio 3.2:1 → WCAG AA requires 4.5:1
MINOR:
2. Mobile layout test → Works, but margin feels tight on 320px
3. Hover state missing on disabled button (desktop)
Design sign-off → BLOCKED until contrast ratio fixed
QA LAYER → TEST COVERAGE
Unit tests → 82% coverage (target 80%, good)
Integration tests → Edge cases missing:
• Concurrent user updates → Race condition possible
• Empty state rendering → Not tested
Functional test → Happy path works, 3 error paths untested
Suggested → Add 2 more tests before merge (30 min effort)
SECURITY LAYER
Input validation → Sufficient (rate limit + sanitize)
Auth check → Correct (user_id derived from session)
Data exposure → None (scoped query by user_id)
Risk → LOW
SHIP DECISION: BLOCKED
Required fixes → Null check (5 min), DB query (15 min), contrast ratio (5 min)
Estimated wait → 1 hour
Re-review → Post-fix, quick approval expected
Alternative → Disable feature in dark mode, ship with flag OFF (not recommended)About this skill
“The feature works locally, but are we actually ready to ship?” This workflow takes a startup feature from a bounded problem statement through implementation and separate engineering, design, QA, security, and release reviews. It exposes the gaps between code that looks finished and behavior that has been verified.
What it does
- Cuts requests into a minimum useful release with explicit acceptance criteria and deferred scope.
- Builds a risk map covering money, permissions, data changes, external services, and user-visible failure states.
- Reviews engineering, design, QA, and security independently, with concrete findings tied to code or missing evidence.
- Chooses tests around failure paths such as retries, duplicate requests, partial success, and mixed application versions.
- Prepares rollout, monitoring, rollback or forward-recovery steps, and documentation appropriate to the change.
- Records unresolved risks and turns actual release outcomes into targeted improvements for the next cycle.
What you get
A scoped delivery plan, implementation or review work within the access provided, and an evidence-backed release verdict. Quick fixes receive focused checks; higher-risk releases receive the full workflow and a concrete list of unresolved gates.
Best for
Startup founders, small engineering teams, and developers using Claude Code to build features while keeping product judgment, verification, and release discipline in the same working session.
SKILL.md preview
---
name: startup-feature-delivery-and-release-review
description: >-
Deliver startup features through scoped planning, implementation, separate product, engineering, design, QA, and security reviews, and evidence-backed release checks. Scale the work to the change's risk and track acceptance criteria through tests, rollout, documentation, and reflection. Use when the user says "take this feature from idea to release", "run the full pre-ship review", "we keep shipping bugs", "is this actually ready to launch?", "my feature works locally but breaks in production", "check engineering, design, and security", or "help us ship this billing change safely".
---
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.