Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "spec-driven-development" with this command: npx skills add Bokazan/skillsmp-bokazan-bokazan-spec-driven-development
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that renders in a browser — DOM inspection, console errors, network analysis, performance profiling, accessibility verification.
Reduces code complexity while preserving exact behavior. Applies Chesterton's Fence principle — understand before removing. Use after implementing features, or on request via /code-simplify.
Safely removes code that no longer justifies its maintenance cost and migrates users to replacements. Use when sunsetting APIs, removing features, or transitioning to new implementations.
Document decisions, not just code. Write Architecture Decision Records for significant technical choices. Use when making architectural decisions, choosing between approaches, or when the same thing needs explaining repeatedly.