requirements-engineering
Master the EARS format to transform ambiguous feature ideas into precise, testable requirements, acceptance criteria, and edge case documentation.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
193 skills found
Master the EARS format to transform ambiguous feature ideas into precise, testable requirements, acceptance criteria, and edge case documentation.
A utility skill for testing multi-skill loading and orchestration within the Sheikh-CLI agentic framework.
Advanced visual regression testing with pixel-perfect and AI-powered diff analysis, cross-browser validation, and responsive design checks to prevent UI regressions in CI/CD pipelines.
Diagnose, isolate, and mitigate LLM context failures like lost-in-middle, poisoning, distraction, and context clash to improve agent reliability.
Automates the documentation of solved technical issues using YAML frontmatter, categorized directories, and institutional knowledge indexing for JUCE plugin development.
Generates structured Handoff Pack prompts for delegating scoped coding tasks to Gemini with clear instructions, acceptance criteria, and output requirements.
A scaffolding tool for generating production-ready Model Context Protocol (MCP) servers, including boilerplate, typed handlers, schema definitions, and test stubs for AI agent integrations.
Browser-based QA automation for web applications. Performs automated site audits, visual regression testing, user flow verification, and issue tracking with real-time browser snapshots.
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, or performing systematic code audits.
Manage major dependency upgrades through systematic compatibility analysis, staged rollout strategies, and automated testing.
CLI-only iOS development agent for Swift, SwiftUI, and UIKit. Handles the full lifecycle: build, debug, test, and release without Xcode.
A framework for applying Test-Driven Development to process documentation, ensuring agent reliability by using pressure scenarios to identify and patch rationalization loopholes.