write-spec
Writes implementation-ready specification files with progress-trackable phases. Activates when: writing a spec, creating a spec file, documenting a feature plan, or when user mentions: write spec, create spec, spec format, spec template.
Implements a specification file phase-by-phase with progress tracking. Activates when: implementing a spec, building from a spec, starting a spec phase, or when user mentions: implement spec, spec file, implement phase, build spec, start phase.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "implement-spec" with this command: npx skills add hihaho/skillsmp-hihaho-hihaho-implement-spec
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.
Writes implementation-ready specification files with progress-trackable phases. Activates when: writing a spec, creating a spec file, documenting a feature plan, or when user mentions: write spec, create spec, spec format, spec template.
MUST USE when creating, updating, or managing AI skills and guidelines. Activates when: creating a new skill, editing existing skills, editing any SKILL.md file, editing any file in .ai/ or .claude/skills/ or .github/skills/, updating coding guidelines, modifying AI instructions, or when user mentions: skill, CLAUDE.md, AGENTS.md, guidelines, AI configuration. ALSO activates when about to write or edit a file matching .claude/skills/**/* or .github/skills/**/* — these are generated files that must not be edited directly.
Runs backend code quality checks in two tiers: Pint + related tests (every change), Pint + PHPStan + Rector + full suite (completion only). Activate after making changes to PHP files, or when user mentions: pint, phpstan, rector, code quality, static analysis, code style, run checks.
Test-driven bug fixing workflow. Activates when: fixing bugs, debugging issues, resolving defects, investigating errors, or when user mentions: bug, fix, broken, not working, error, issue, defect, regression.