lucasilverentand/post-release-review
plugins/project-docs/skills/post-release-review/SKILL.md
Writes post-release review documents from the project-docs template. Use when the user asks for a post-release review, wants a retrospective after shipping or abandoning work, needs lessons and follow-up issues captured, or is filling post-release-review.md.
$ install --global
skillsauthnpx skillsauth add lucasilverentand/skills post-release-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 7:16 AM176.2s2 files scanned
SKILL.md
- name:
- post-release-review
- description:
- Writes post-release review documents from the project-docs template. Use when the user asks for a post-release review, wants a retrospective after shipping or abandoning work, needs lessons and follow-up issues captured, or is filling post-release-review.md.
Post-Release Review
Use this skill to compare what happened against the plan and turn useful lessons into durable decisions or follow-up work.
Decision tree
- What is the user asking for?
- A new post-release review -> read
../../README.mdandreferences/template.md, then draft the review in the requested destination. - The release has not shipped yet -> use the
release-readinessskill until there is an outcome to review. - A decision worth preserving -> use the
decision-recordskill and link it from the review. - Follow-up work outside the review -> file or draft issues only when the user asks, or when repo instructions require filing later work.
- Something else -> ask what shipped, stalled, rolled back, or was abandoned.
- A new post-release review -> read
Workflow
- Read
../../README.mdfor shared conventions and relationship rules. - Read
references/template.mdbefore drafting or editing. - Gather what happened, what changed from the plan, what worked, what did not, decisions worth keeping, debt created, and follow-up issues.
- Link release readiness, feature specs, decision records, incidents, PRs, changelog entries, and follow-up issues where they explain the outcome.
- Keep the review factual. Avoid blame language and vague lessons that no one can act on.
- Convert durable decisions and follow-up work into linked records instead of burying them in prose.
Document contract
- When to write: After something ships, stalls, rolls back, or gets abandoned and the team needs to preserve what happened.
- How many: One per release or abandoned effort.
- Owns: Outcome, plan changes, what worked, what did not, preserved decisions, debt created, and follow-up issues.
- Link instead of duplicating: Launch evidence belongs in release readiness; product behavior belongs in feature specs; precedent belongs in decision records.
Related Skills
lucasilverentand/foundations
development
VerifiedTrustedCommunity
Cross-platform Apple Human Interface Guidelines: color, typography, layout, materials, motion, accessibility, SF Symbols, branding, plus shared UI elements (activity views, rating indicators, web views, …) and meta sections (components, patterns, technologies). Use when the design topic is platform-agnostic. User says: "iOS color tokens", "SF Symbols", "Apple typography", "dark mode guidance".
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-workflow
development
VerifiedTrustedCommunity
Guides a full system design from idea to spec — sequences requirements gathering, architecture decomposition, data modeling, API design, and document writing into a coherent workflow with clear handoffs. Use when the user asks to "design a system", "build X from scratch", "architect something end-to-end", "plan a new service", or has a broad design ask that spans multiple concerns. Also use when the user says things like "I need to build X" without specifying which aspect to start with. This is the entry point for any design task that isn't clearly scoped to a single skill (data model only, API only, etc.).
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-system
development
VerifiedTrustedCommunity
Synthesizes build-ready design systems and DESIGN.md files from chat briefs, screenshots, moodboards, videos, URLs, live pages, or local image folders while preserving the target product identity. Use when the user asks to "make a design system from these screenshots", "turn this moodboard into DESIGN.md", "extract the design language from this video", "define the UX vibe and rules from these references", or create cohesive UI rules from visual inspiration.
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-review
development
VerifiedTrustedCommunity
Reviews and critiques an existing or proposed system design — flags single points of failure, missing non-functional requirements, scaling bottlenecks, security gaps, operational blind spots, unjustified tech choices, and places where the design will fall over under load or failure. Produces a structured review with severity-tagged findings, not just vibes. Use when the user asks for a second opinion on an architecture, requests a design review, wants feedback on a proposed system, pastes a design doc, or says things like "review this design", "what's wrong with X", "poke holes in this", or "is this a good architecture".
3SKILL.mdUpdated Jun 13, 2026