create▌

Create GitHub Issues automatically from implementation plan phases. \n \n Analyzes implementation plan files to identify phases and generates one issue per phase \n Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format \n Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed \n Includes phase details, requirements, and context in issue descriptions with appropriate labels \n

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Google Sheets spreadsheet template for expense tracking with automated setup and sharing. \n \n Creates a new spreadsheet with standard expense columns (Date, Category, Description, Amount) and sample entries \n Includes built-in sharing capabilities to grant read or edit access to team members via email \n Requires gws-sheets and gws-drive skills; uses Google Workspace APIs for spreadsheet and file management \n

Create a Google Meet meeting space and email the join link to participants. \n \n Requires two prerequisite skills: gws-meet for space creation and gws-gmail for sending invitations \n Creates an open-access meeting space via the Meet API and extracts the meeting URI from the response \n Automates sharing the join link by composing and sending an email with the meeting details to specified recipients \n

Create structured, machine-readable implementation plans for features, refactoring, upgrades, and infrastructure changes. \n \n Generates deterministic, AI-executable plans with discrete phases, atomic tasks, and explicit completion criteria \n Enforces strict template compliance with standardized identifier prefixes (REQ-, TASK-, GOAL-, etc.) and machine-parseable formats \n Includes mandatory sections for requirements, implementation phases, dependencies, testing, risks, and alternatives \n Su

Generates formal, AI-optimized specifications for GitHub Actions workflows to standardize documentation and enable maintenance. \n \n Produces structured markdown specifications with execution flow diagrams, job dependency matrices, and requirement tables designed for token efficiency \n Covers functional, security, and performance requirements alongside input/output contracts, error handling strategies, and quality gates \n Includes sections for monitoring, compliance, edge cases, and change ma

Generate structured, AI-optimized specification documents with standardized templates and machine-readable formatting. \n \n Creates specification files in /spec/ directory following naming convention spec-[purpose]-[type].md with YAML front matter for metadata \n Enforces structured markdown with 11 standard sections covering purpose, requirements, interfaces, acceptance criteria, and validation \n Includes explicit guidelines for unambiguous language, acronym definitions, and self-contained do

Generates standardized AGENTS.md files to help AI coding agents understand and work with your repository. \n \n Provides a template-driven approach for creating agent-focused documentation that complements README.md with technical setup, workflow, and testing instructions \n Covers essential sections including project overview, setup commands, development workflow, testing, code style, build/deployment, and PR guidelines \n Supports monorepo structures with guidance for creating AGENTS.md files

Guide for creating AGENTS.md files for project-specific inline rules.

You're using a skill that will guide you through setting up AI configuration in your application. Your job is to explore the codebase to understand the use case and stack, choose agent vs completion mode, create the config following the right path, and verify it works.