blueprint-optimize

Sync Linear tickets, finalize commits, and generate postmortems after PR merges.

1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/morris-y/blueprint-skills --skill blueprint-optimize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint-optimize
Source: https://github.com/morris-y/blueprint-skills/tree/main/skills/blueprint-optimize
Command: npx skills add https://github.com/morris-y/blueprint-skills --skill blueprint-optimize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use after PR merge to complete the iteration cycle. Supports Ralph Loop for iterative PM refinement. Syncs Linear status, commits with standards, creates Postmortems for significant incidents, and crystallizes high-frequency rules into CLAUDE.md.

Core Features & Use Cases

  • Status sync & finalization: Mark Linear tickets as Done and attach closing summaries.
  • Postmortem creation & CLAUDE.md derivation: Create thorough postmortems for significant incidents and preview high-frequency rules before writing to CLAUDE.md.
  • Ralph Loop support (optional): Iteratively refine postmortems for quality and depth when incidents are complex.
  • Use Case: After a merged PR, run blueprint-optimize to close the loop, capture lessons, and update CLAUDE.md to improve future responses.

Quick Start

Run blueprint-optimize after a PR merge to finalize the iteration, generate postmortem, and update CLAUDE.md.

Frequently Asked Questions about blueprint-optimize

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

FAQPage Schema
How do I automate post-merge iteration closure and sync Linear ticket status?

Automate post-merge iteration closure by running blueprint-optimize to sync Linear tickets to Done, finalize commits, and generate postmortems. This ensures consistent PM processes and documentation after a PR merge.

How do I generate a postmortem for significant incidents after a PR merge?

Generate a postmortem for significant incidents by running blueprint-optimize after a PR merge. The skill creates thorough incident analyses and optionally uses Ralph Loop refinement to iteratively improve postmortem quality for complex scenarios.

Can I update CLAUDE.md with high-frequency rules derived from postmortems?

Update CLAUDE.md by deriving high-frequency rules from finalized postmortems. The skill previews these crystallized rules before writing them to CLAUDE.md, ensuring future responses incorporate lessons learned from the iteration.

What is the best way to finalize commits and attach closing summaries to Linear tickets?

Finalize commits and attach closing summaries to Linear tickets by executing blueprint-optimize post-merge. It enforces commit standards, marks tickets as Done, and embeds closing summaries directly within the Linear status sync.

Does the Ralph Loop support iterative PM refinement for complex incidents?

The Ralph Loop supports iterative PM refinement for complex incidents. Applied optionally during postmortem creation, it iteratively enhances the analysis depth and quality to capture comprehensive incident insights.

When do I need to run post-merge iteration closure and postmortem generation?

Run post-merge iteration closure immediately after a PR merges to complete the iteration cycle. It is needed to sync Linear status, create postmortems for significant incidents, and crystallize high-frequency rules into CLAUDE.md.