Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

ngvoicu

@ngvoicu source repo

4 published skills

  1. ▌
    Specmint Tdd · ngvoicu
    TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "red green refactor", "run the tests", "generate openapi". Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging.
    0
    installs
  2. ▌
    Specmint Core · ngvoicu
    Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement the spec", "implement phase N", "implement all phases", "generate openapi", or exits plan mode (offer to save as a spec). Also trigger when a `.specs/` directory exists at session start. Do NOT trigger on general feature requests, coding tasks, or questions that don't mention specs or forging — those are normal coding tasks, not spec management.
    0
    installs
  3. ▌
    Specmint Tdd HTML · ngvoicu
    TDD-first spec management for AI coding workflows, producing canonical SPEC.html files with red-green-refactor state. Use this companion when the user explicitly mentions specs, forging, structured planning, resume/status, implementing a spec, red-green-refactor, or running tests. Do NOT trigger on ordinary coding tasks that do not ask for spec management.
    0
    installs
  4. ▌
    Specmint Core HTML · ngvoicu
    Persistent spec management for AI coding workflows, producing canonical SPEC.html files. Use this companion when the user explicitly mentions specs, forging, structured planning, resume/status/pause/switch, implementing a spec, or generating OpenAPI docs. Do NOT trigger on ordinary coding tasks that do not ask for spec management.
    0
    installs