alexbruno/dev-skills

incremental-implementation

Build features and refactorings in small, verified vertical slices instead of large unverified code dumps.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/alexbruno/dev-skills --skill incremental-implementation

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Incremental Implementation

Deliver changes in thin, verifiable increments—one working slice at a time. Never write an entire multi-file feature in a single unverified pass.

Core Rule

One slice, one verification cycle. Do not start the next slice while the current slice has failing tests, type errors, or a broken build.

When to Apply

  • Executing steps from workflow/PLAN.md or tasks from workflow/TASKS.md.
  • Any change touching two or more files or exceeding ~100 lines of code.
  • Refactoring existing modules where behavior must remain intact at every step.

The Increment Loop

For each step in workflow/PLAN.md (or task in workflow/TASKS.md):

  1. Scope the Slice: Pick the smallest cohesive unit that delivers testable progress toward workflow/SPEC.md.
  2. Implement Minimally: Write only the code required for this slice—avoid speculative scaffolding for future slices.
  3. Test & Verify Immediately: Run targeted unit/integration tests, typecheck, and linter to confirm the slice works and introduces no regressions.
  4. Checkpoint: Update status in workflow/PLAN.md or workflow/TASKS.md (e.g., mark done), and create a clean commit/checkpoint when appropriate so rollback is effortless.
  5. Repeat: Advance to the next slice only after the current one is green.

Slicing Strategies

Choose the slicing strategy that best fits the work:

  • Vertical Slices (Default): Implement one thin end-to-end capability across layers (e.g., schema -> service -> endpoint -> test) rather than building all backend files first and all frontend/test files last.
  • Risk-First Slicing: Tackle the highest-uncertainty assumption, integration, or performance bottleneck in the earliest slice so surprises surface immediately.
  • Contract-First Slicing: Define types, interfaces, and test assertions first, verify they compile/fail as expected, then implement the concrete behavior.

Guardrails

  • No stacked brokenness: Fix failing checks in the current slice before moving on.
  • Keep diffs reviewable: If a slice grows too large, split it into smaller sub-slices before continuing.
  • Stay aligned with `SPEC.md`: Do not add unrequested features while implementing a slice.
du même dépôt

Autres Skills

Tous les Skills
alexbruno
Communauté

architect-worker

Role-based multi-agent software engineering pattern separating high-level architecture, specification, planning, and code review (Architect) from focused code implementation and verification (Worker). Use this skill whenever assigned the Architect or Worker role (in any language), or when coordinating work between planning/review agents and implementation agents via workflow/.

Installations / 1h
1
GitHub Stars
0
Mis à jour
13 nov.
alexbruno
Communauté

changelog-management

Maintain and update a standardized root CHANGELOG.md following Keep a Changelog and Semantic Versioning. Use this skill to initialize or update changelog entries, categorize changes, prepare release cuts, and proactively prompt the user when notable changes warrant updating the changelog.

Installations / 1h
1
GitHub Stars
0
Mis à jour
13 nov.
alexbruno
Communauté

code-review

Perform structured, multi-dimensional code reviews aligned with the spec-driven-workflow (workflow/SPEC.md, workflow/PLAN.md, workflow/REVIEW.md). Use this skill after implementing a feature or bug fix, before merging a PR, or when reviewing changes written by another agent or human.

Installations / 1h
1
GitHub Stars
0
Mis à jour
13 nov.
alexbruno
Communauté

code-simplification

Simplify code for human readability, clarity, and directness without changing behavior. Use this skill after implementing a feature, during refactoring, or when addressing code review feedback—especially when code feels over-engineered, deeply nested, or takes unnecessary detours to do simple things.

Installations / 1h
1
GitHub Stars
0
Mis à jour
13 nov.