Reviews PRD and spec for consistency, completeness, and clarity; optionally compares against uploaded mocks, wireframes, or fat-marker sketches and flags design inconsistencies. Use when the user wants a design or document review before implementation, or when running the feature-builder workflow after PRD and spec…
Keeps the project's document library consistent after new or changed PRDs and specs. Discovers or uses the project's index, README, feature/capability pages, and spec listings; proposes and applies updates so new docs are discoverable. Use when new docs are added or changed and the user wants index and related pages…
Scaffolds the standard documentation folder structure (README, productBrief, audienceProfiles, designDetails, features, specDocs, productRequirementsDocs, images). Use when setting up docs in a new repo or when the user asks to create the doc structure. When adding a new feature page, use the feature-template.md…
End-to-end feature development from discovery through PRD, spec, design review, doc library cleanup, and optional implementation. Orchestrates sub-skills in phases with confirmation gates. Use when building a new feature or making significant feature changes and you want the full workflow.
Produces a Product Requirements Document (PRD) from problem context. Use when the user needs a PRD written or updated, or when building a feature and a PRD is the next deliverable. Works standalone or as part of the feature-builder workflow.
Produces a Spec Doc (feature summary, problems, audience, features, success metrics, and user flows). Use when the user needs a spec document written or updated, or when a PRD exists and the next deliverable is a spec. Works standalone or as part of the feature-builder workflow.
★not rated 2 8mo agoA63 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: