5d-reflect
Extract learning from completed work to improve future cycles. Use when: (1) After VERIFY phase shows feature complete, (2) End of development iteration, (3) User asks for 'retrospective,' 'lessons learned,' or 'what went well/wrong,' (4) Before starting next major feature. This phase prevents repeating mistakes and compounds learning.
What this skill does
# REFLECT Phase Extract learning to evolve the development process itself. ## Reflection Dimensions ### Width: Domain Learning - What domain knowledge did we gain? - What domains did we neglect that caused problems? - What adjacent expertise would have helped? ### Depth: Thinking Quality - Where did we get stuck in dogmatic (Level 2) thinking? - Where did we successfully hold contradictions (Level 3)? - What novel insights emerged (Level 4)? ### Height: Skill Dependencies - What adjacent skills blocked progress? - What capability unlocked other capabilities? - What should be learned before next iteration? ### Quadrants: Perspective Coverage - Which quadrant did we neglect? - Which quadrant dominated (possibly over-indexed)? - Where did Collective dimensions cause surprises? ### Time: Pattern Recognition - What should we "transcend and include" next time? - What patterns repeated from past projects? - What's the trajectory—are we improving? ### Identity Trap Analysis - Where did we stop thinking because it felt threatening? - What ideas did we defend rather than examine? - What beliefs did we inherit that we should question? - Where did attachment to being "right" block progress? ## Reflection Questions ### What Went Well - What decisions saved time or prevented problems? - What phase worked smoothly? - What should we repeat? ### What Went Poorly - Where did we waste effort? - What surprises should have been anticipated? - What phase broke down? ### Process Improvements - What should change in our workflow? - What new checks or steps are needed? - What should we stop doing? ## Output Format ``` ## Iteration Retrospective ### Dimension Analysis **Width (domains):** - Gained: [knowledge acquired] - Missed: [domains we should have considered] **Depth (thinking levels):** - Got stuck: [where we were dogmatic] - Breakthrough: [where we synthesized well] **Height (skills):** - Blocked by: [missing capability] - Unlocked: [capability we developed] **Quadrants:** - Neglected: [which quadrant] - Over-indexed: [which quadrant] ### What Worked - [success 1] - [success 2] ### What Didn't - [failure 1]: [root cause] - [failure 2]: [root cause] ### Process Changes for Next Iteration - [change 1] - [change 2] ### Carry Forward [Key insight to remember for future work] ``` ## Exit Criteria Reflection complete when: - All dimensions examined - At least one process improvement identified - Learnings documented for future reference Return to ORIENT for next feature with accumulated wisdom.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.