project-management
11
incident-postmortem
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
proflead
business
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
project-management
11
deliberation-debate-red-teaming
Use when testing plans or decisions for blind spots, need adversarial review before launch, validating strategy against worst-case scenarios, building consensus through structured debate, identifying attack vectors or vulnerabilities, user mentions "play devil's advocate", "what could go wrong", "challenge our assumptions", "stress test this", "red team", or when groupthink or confirmation bias may be hiding risks.
lyndonkl
business
project-management
11
domain-storytelling
Collaborative domain modeling through pictographic stories. Use when gathering requirements, understanding business workflows, onboarding team members, or preparing for event storming. Follows Stefan Hofer & Henning Schwentner's methodology with actors, work objects, and activities.
melodic-software
business
project-management
11
team-topologies
Four fundamental team types and interaction modes from Team Topologies
melodic-software
business
sales-marketing
11
alignment-values-north-star
Use when teams need shared direction and decision-making alignment. Invoke when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or setting behavioral standards. Use when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
lyndonkl
business
project-management
11
phase-implement
Coordinate implementation phase by delegating tasks and ensuring code quality. Use during implementation phase to manage engineer tasks.
mvillmow
business
project-management
11
css-layout-helper
Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.
proflead
business
project-management
11
code-review-communication
Frameworks for giving and receiving code review feedback effectively. Use for PR comments, review strategies, handling disagreements, and balancing thoroughness with kindness.
melodic-software
business
project-management
11
mentoring-developers
Frameworks for effective mentoring and knowledge transfer. Use for 1:1 meetings, pair programming, onboarding, teaching technical concepts, and developing junior engineers.
melodic-software
business
project-management
11
decomposition-reconstruction
Use when dealing with complex systems that need simplification, identifying bottlenecks or critical failure points, redesigning architecture or processes for better performance, breaking down problems that feel overwhelming, analyzing dependencies to understand ripple effects, user mentions "this is too complex", "where's the bottleneck", "how do we redesign this", "what are the key components", or when optimization requires understanding how parts interact.
lyndonkl
business
project-management
11
requirements-quality
Requirements quality assessment and improvement. Use when evaluating requirements against INVEST criteria, improving clarity, detecting ambiguity, or ensuring completeness. Provides quality checklists, refinement patterns, and MoSCoW prioritization guidance.
melodic-software
business
project-management
11
performance-budgeting
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
proflead
business
project-management
11
constraint-based-creativity
Use when brainstorming feels stuck or generates obvious ideas, need to break creative patterns, working with limited resources (budget/time/tools/materials), want unconventional solutions, designing with specific limitations, user mentions "think outside the box", "we're stuck", "same old ideas", "tight constraints", "limited budget/time", or seeking innovation through limitation rather than abundance.
lyndonkl
business
project-management
11
stakeholders-org-design
Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".
lyndonkl
business
project-management
11
runbook-creation
Operational runbook templates for incident response and procedures
melodic-software
business
project-management
11
vulnerability-management
Vulnerability lifecycle management including CVE tracking, CVSS scoring, risk prioritization, remediation workflows, and coordinated disclosure practices
melodic-software
business
project-management
11
team-topology-design
Team Topologies methodology for organizational design. Covers the four fundamental team types, three interaction modes, cognitive load assessment, Inverse Conway Maneuver, and team evolution patterns. Use when designing team structures that align with architecture.
melodic-software
business
project-management
11
backlog-update
Reminder to update backlog.org before commits or when finishing significant work. Use before committing changes, after completing implementation from plan mode, or when wrapping up a work session. This skill ensures the project's task tracking in backlog.org stays current with actual progress. Trigger when about to commit, exiting plan mode, or when user says "done", "let's commit", "wrap up", or similar.
farra
business
project-management
11
reviews-retros-reflection
Use when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), team health checks, process improvement sessions, celebrating wins while learning from misses, establishing continuous improvement habits, or when user mentions "retro", "retrospective", "what went well", "lessons learned", "review meeting", "reflection", or "how can we improve".
lyndonkl
business
project-management
11
track-implementation-progress
Track implementation progress against plan. Use to monitor component delivery and identify blockers.
mvillmow
business
project-management
11
revising-findings
Implement findings from verification reports with scope-based parallel workflow
cipherstash
business
project-management
11
agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
mvillmow
business
project-management
11
postmortem
Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.
lyndonkl
business