Generalize implement-spec skill to support non-faker specs #40

Overview

Expand the implement-spec skill so it can handle general (non-faker) specs — workflow tooling, build config, documentation changes — in addition to new Java faker providers.

Changes

SKILL.md updates

• Description broadened from "Java faker feature" to any spec type
• Step 1 now includes a classification step: identify whether the spec is a new faker or general (workflow, tooling, config, docs)
• Step 1b added: read LEARNINGS.md before touching any code
• Step 3 branch naming now covers both patterns:
  • New faker: add-<feature-name>-faker
  • General: a descriptive kebab-case name (e.g. add-pre-commit-hooks, update-build-config)
• Step 4 split into conditional paths — faker path unchanged; new general path added
• Step 5 (new): reflect and update LEARNINGS.md before committing
• Step numbers renumbered accordingly (old 5→6, old 6→7)

Verification

• SKILL.md description is generic (no mention of "Java faker")
• Step 1 contains classification logic
• Step 1b reads LEARNINGS.md
• Step 3 branch naming covers both spec types
• Step 4 has separate guidance for faker vs general specs
• Step 5 captures learnings before commit
• Step numbers are sequential (1, 1b, 2, 3, 4, 5, 6, 7)