gj-retro-learnings
Extract iteration retrospectives, process learnings, improvement actions, and ai-context-summary content from GitLab Issues, MRs, tests, releases, and demo-run artifacts. Use when closing a milestone or preparing durable AI context.
Works with
--- name: gj-retro-learnings description: Extract iteration retrospectives, process learnings, improvement actions, and ai-context-summary content from GitLab Issues, MRs, tests, releases, and demo-run artifacts. Use when closing a milestone or preparing durable AI context. license: MIT --- # GJ Retro Learnings ## Workflow 1. Read the project control Issue, milestone, requirement, solution, tasks, test, release, retro, and merged MRs. 2. Summarize what shipped and what changed. 3. Separate process friction from product or code defects. 4. Identify which changes belong in long-term context: - `docs/context/current-state.md` - `docs/modules/*.md` - `.ai/context-index.yml` - ADRs 5. Identify document quality issues: - missing PRD/design/prototype/solution/test/release docs. - stale docs that misled implementation, review, or QA. - templates or standards that need improvement. 6. Generate `docs/iterations/<iteration>/06-retro.md`. 7. Generate `docs/iterations/<iteration>/ai-context-summary.md`. ## Output ```markdown ## Retro Summary Shipped: What worked: What failed or slowed down: Defects and root causes: AI suggestions adopted: AI misses: Process improvements: Documentation improvements: Long-term context updates: ai-context-summary draft: ``` ## References Read `references/demo-run.md` for the first-run retro example.
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

