difficult-conversations
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
draft-email
Draft a professional email using the What-Why-How framework. Use when you need to compose emails to colleagues, stakeholders, or leadership.
feedback-conversations
Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.
interview-skills
Frameworks for technical interviews and salary negotiation. Use for behavioral interview prep (STAR method), technical interview communication, offer evaluation, and compensation negotiation strategies.
mentoring-developers
Frameworks for effective mentoring and knowledge transfer. Use for 1:1 meetings, pair programming, onboarding, teaching technical concepts, and developing junior engineers.
plan-career-goals
Create structured career goals with timelines, actions, milestones, and accountability measures.
professional-communication
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.
promotion-preparation
Building promotion cases, brag documents, tracking wins, and self-advocacy for career advancement. Use when preparing for promotions, documenting accomplishments, or building your case for advancement.
resume-optimization
Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
review-comment
Generate a well-structured code review comment using Conventional Comments format. Helps give clear, actionable feedback on PRs.
stakeholder-communication
Adapting technical communication for different audiences - engineers, product managers, executives, and customers. Use when communicating across functions, translating technical concepts, presenting to leadership, or building shared understanding with non-technical stakeholders.
structure-presentation
Create a structured presentation outline using the What-Why-How framework. Use when preparing talks, demos, or technical presentations.
team-effectiveness
Building high-performing teams through psychological safety, diversity leverage, inclusive practices, and healthy team dynamics. Use when improving team collaboration, addressing team dysfunction, building inclusive environments, or developing team culture.
technical-presentations
Create and deliver effective technical presentations, demos, and talks. Provides frameworks for structuring content, designing slides, and handling live demos.
track-win
Document an accomplishment in brag document format with proper categorization and impact metrics.
write-1on1-agenda
Generate a structured agenda for a 1:1 meeting with your manager, mentor, or direct report. Includes discussion questions and follow-up sections.
write-cfp
Draft a compelling conference proposal (Call for Papers) that gets accepted. Use when submitting to conferences, meetups, or internal tech talks.
adr-create
Create Architecture Decision Record from specification context.
asyncapi-authoring
Author and validate AsyncAPI 3.0 specifications for event-driven API design, message brokers, and async communication patterns
canonical-spec-format
Canonical specification format reference. Use when understanding the canonical spec schema, field requirements, provider-agnostic specification structure, or validating specifications against the schema.
constitution
Create or update the project constitution file (.constitution.md) for Spec Kit workflow.
contract-first-design
Design and manage API contracts before implementation using OpenAPI and AsyncAPI specifications for contract-first development
convert
Convert specification between formats (EARS, Gherkin, Kiro, canonical).
ears-author
Interactive EARS pattern authoring assistant. Guides through pattern selection and requirement construction.
ears-authoring
EARS requirement pattern authoring. Use when writing requirements using EARS patterns (Ubiquitous, State-Driven, Event-Driven, Unwanted, Optional, Complex). Provides pattern templates, validation, and examples.
gherkin-author
Interactive Gherkin scenario authoring. Guides through Given/When/Then construction with BDD best practices.
gherkin-authoring
Gherkin acceptance criteria authoring. Use when writing Given/When/Then scenarios, feature files, or BDD-style specifications. Provides syntax reference, best practices, and Reqnroll integration guidance.
gherkin-convert
Convert specifications to/from Gherkin/BDD format.
implement
Guide implementation of specification tasks. Phase 4 of Spec Kit workflow.
kiro-integration
AWS Kiro specification patterns and synchronization. Use when working with Kiro IDE, syncing requirements.md/design.md/tasks.md files, or configuring steering files for AI agent context.
kiro-sync
Synchronize specifications with AWS Kiro format (requirements.md, design.md, tasks.md).
openapi-authoring
Author and validate OpenAPI 3.1 specifications for REST API design, following API-first and contract-first development practices
plan
Generate an implementation plan from a specification. Phase 2 of Spec Kit workflow.
refine
Refine specification with AI-assisted improvements.
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.
spec-management
Central authority for specification-driven development. Use when working with requirements, specifications, acceptance criteria, or any spec-driven workflow. Provides navigation to specialized skills and delegates to docs-management for official documentation.
speckit-run
Execute the complete GitHub Spec Kit 5-phase workflow from constitution to implementation.
speckit-workflow
GitHub Spec Kit 5-phase workflow. Use when following the Constitution → Specify → Plan → Tasks → Implement cycle. Provides phase guidance, file templates, and workflow orchestration.
status
Display specification status dashboard showing workflow progress, quality scores, and pending items.
userstory-author
Author Agile-style user stories with linked acceptance criteria.
validate
Validate specification against schema and quality rules.
api-design-fundamentals
Use when designing APIs, choosing between REST/GraphQL/gRPC, or understanding API design best practices. Covers protocol selection, resource modeling, and API patterns.
api-review
Review API design for best practices, consistency, and common issues
api-versioning
Use when planning API versioning strategy, handling breaking changes, or managing API deprecation. Covers URL, header, and query parameter versioning approaches.
cdn-architecture
Use when designing content delivery networks, caching strategies, or global content distribution. Covers CDN architecture, cache hierarchies, origin shielding, cache invalidation, and edge optimization.
chaos-engineering-fundamentals
Use when implementing chaos engineering, designing fault injection experiments, or building resilience testing practices. Covers chaos principles and experiment design.
chaos-plan
Design chaos engineering experiments for a system - identifies failure modes, creates experiment hypotheses, and generates GameDay plans
data-architecture
Use when designing data platforms, choosing between data lakes/lakehouses/warehouses, or implementing data mesh patterns. Covers modern data architecture approaches.
data-flow
Design data pipeline architecture for a given data flow scenario
design-interview-methodology
4-step framework for system design interviews. Use when preparing for technical interviews, practicing whiteboard design, or structuring architectural discussions. Covers requirements gathering, high-level design, deep dives, and wrap-up.
Page 545 of 1447 · 72311 results