📦

lean-build

Name: lean-build
Author: juliusbrussee

Révision du contenu r1 Sûr

Build Features Without Speculative Scope

Feature work often grows beyond acceptance needs and weakens architectural ownership. Lean Build defines a narrow outcome, reuses repository patterns, and stops after focused verification.

Prend en charge: Claude Codex Code(CC)

🥉 78 Bronze

Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "lean-build" from https://skillstore.io/skills/juliusbrussee-lean-build.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-lean-build/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/juliusbrussee-lean-build.md manifest signé GET /api/skills/juliusbrussee-lean-build/manifest lockfile signé GET /api/skills/juliusbrussee-lean-build/lockfile

Tester

Utilisation de « lean-build ». Add saved filters to the issue list without introducing new configuration.

Résultat attendu:

Acceptance covers saving, selecting, and deleting filters through existing preference ownership. Non-goals exclude sharing, import, export, and filter templates.

Utilisation de « lean-build ». Connect the current notification flow to a second provider.

Résultat attendu:

Trace the existing notification entry point, provider boundary, retry ownership, and test path.
Add only the provider implementation and required registration.
Stop after focused delivery and failure-path checks pass.

Utilisation de « lean-build ». Fix duplicate status updates appearing in two interface views.

Résultat attendu:

Move deduplication to the shared status owner, preserve both views, and verify the common update path plus focused regression coverage.

Audit de sécurité

Sûr

v1 • 12/08/2026 Ouvrir le rapport versionné

No security findings were identified in the prompt-only skill. It contains implementation guidance without executable code, external access, data collection, or prompt injection.

Fichiers analysés

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/juliusbrussee-lean-build/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/juliusbrussee-lean-build/security.svg)](https://skillstore.io/skills/juliusbrussee-lean-build?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/juliusbrussee-lean-build?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-lean-build/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/juliusbrussee-lean-build.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

juliusbrussee. (2026). lean-build security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-lean-build/audits/1

Citation BibTeX

@techreport{juliusbrussee-juliusbrussee-lean-build-2026,
  author = {juliusbrussee},
  title = {lean-build security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/juliusbrussee-lean-build/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lean-build security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "juliusbrussee"
date-released: "2026-08-12"
url: "https://skillstore.io/skills/juliusbrussee-lean-build/audits/1"
identifiers:
  - type: other
    value: "skillstore:juliusbrussee-lean-build:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Deliver a Product Slice

Implement one observable user outcome across the repository while excluding unrelated enhancements.

Constrain an Integration

Add a required integration using existing ownership boundaries and only necessary lifecycle changes.

Correct Shared Behavior

Fix a narrow behavior at its owning layer and verify the affected path.

Essayez ces prompts

Define the Smallest Outcome

Use $lean-build to implement [feature]. First state observable acceptance criteria and explicit non-goals from this repository.

Reuse Repository Ownership

Use $lean-build for [feature]. Trace the entry point and owning layers, then implement the smallest coherent path using existing patterns.

Evaluate a Focused Refactor

Use $lean-build to add [behavior]. Refactor only where direct patching would duplicate behavior, weaken ownership, or hide the root cause.

Deliver a Constrained Integration

Use $lean-build to integrate [service]. Define lifecycle needs, material tradeoffs, focused verification, and the exact stop condition before implementation.

Bonnes pratiques

Provide the feature request, repository context, and expected user-visible result.
Confirm acceptance criteria and non-goals before implementation begins.
Run focused tests on the complete path and stop when acceptance passes.

Éviter

Do not add extensibility, providers, modes, or configuration for hypothetical future needs.
Do not force cross-layer behavior into one local patch when ownership belongs elsewhere.
Do not continue polishing after acceptance passes without a new requirement.

Foire aux questions

What types of work fit Lean Build?

It fits new behavior, product slices, integrations, and narrow fixes where scope growth is a concern.

Does the skill always choose the fewest changed files?

No. It favors the smallest coherent outcome across responsible layers, which may require several focused changes.

When does it recommend refactoring?

It recommends refactoring when a direct patch duplicates behavior, weakens ownership, or hides the root cause.

Will it add configuration for future flexibility?

Only when acceptance or lifecycle design requires configuration. Speculative options remain out of scope.

How does it decide when to stop?

It stops when the observable acceptance path passes focused verification and only material omissions remain.

Does Lean Build replace broader testing?

No. It emphasizes focused proof for the changed path, while broader validation remains a repository and release responsibility.

Détails du développeur

Auteur

juliusbrussee

Licence

MIT

Révision Skillstore

Avis de version

L’auteur n’a déclaré aucune version.

Dépôt

https://github.com/juliusbrussee/caveman/tree/a0109974ea3258a14aadaef1ed1f8ff2837d30d5/skills/lean-build

Réf

7b8c859294bb987ad70ef94d6499a7aa97cc8252

Récence de maintenance

13/08/2026

Utilisation

0 téléchargements · 0 vues

Structure de fichiers

📁 agents/

📄 openai.yaml

📄 SKILL.md