spec▌

Reverse-engineer undocumented codebases to extract specifications, architecture, and observable behavior patterns. \n \n Uses two analytical perspectives: Arch Hat for system architecture and data flows, QA Hat for observable behaviors and edge cases \n Employs systematic exploration with Glob, Grep, and Read tools to map code structure, entry points, configuration, and API routes before documentation \n Documents extracted requirements in EARS format (Ubiquitous, Event-driven, State-driven, Opt

Official GitHub Spec-Kit integration providing a 7-phase constitution-driven workflow for feature development.

Structured product requirements documents with problem statements, user stories, and success metrics. \n \n Guides PRD structure across eight sections: problem statement, goals, non-goals, user stories, requirements (P0/P1/P2), success metrics, open questions, and timeline considerations \n Provides frameworks for user story writing, MoSCoW requirement prioritization, and acceptance criteria in Given/When/Then format \n Includes guidance on defining leading and lagging success metrics with speci

$22

Comprehensive feature specification and planning guide for software engineers, product managers, and technical leads. Contains 42 rules across 8 categories, prioritized by impact to prevent scope creep and ensure project success.

A comprehensive methodology for systematic software feature development that ensures quality, maintainability, and successful delivery through structured planning.

Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.

Convert Notion specs into linked implementation plans, tasks, and progress tracking. \n \n Automates the workflow from spec discovery through task creation: search and fetch specs, parse requirements, generate implementation plans, and create tracked tasks in Notion. \n Includes templates for quick vs. full implementation plans, task creation patterns, and progress update cadences to match project scope. \n Provides reference guides for requirement extraction, task sizing (1–2 day chunks), depen

Structured workflow for requirements analysis, technical design, and task planning across feature development and architecture projects. \n \n Enforces four sequential phases: requirements documentation with EARS syntax, technical solution design, task breakdown, and execution, with user confirmation required between each phase \n Integrates UI design skill for frontend-heavy projects, determining design style and color palette during requirements phase \n Provides templates for requirements doc

Verifies code implements exactly what documentation specifies for blockchain audits. \n \n Performs deterministic, line-by-line semantic analysis of code against specification documents, whitepapers, or design docs to identify gaps and misalignments \n Extracts specification intent and code behavior into structured intermediate representations (Spec-IR, Code-IR, Alignment-IR) with full traceability and confidence scores \n Classifies divergences by severity (critical, high, medium, low) with evi