lean-build
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.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "lean-build". Add saved filters to the issue list without introducing new configuration.
Expected outcome:
Acceptance covers saving, selecting, and deleting filters through existing preference ownership. Non-goals exclude sharing, import, export, and filter templates.
Using "lean-build". Connect the current notification flow to a second provider.
Expected outcome:
- 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.
Using "lean-build". Fix duplicate status updates appearing in two interface views.
Expected outcome:
Move deduplication to the shared status owner, preserve both views, and verify the common update path plus focused regression coverage.
Security Audit
SafeNo security findings were identified in the prompt-only skill. It contains implementation guidance without executable code, external access, data collection, or prompt injection.
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/juliusbrussee-lean-build/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/juliusbrussee-lean-build?utm_source=security_passport_badge)HTML badge
<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>Embed card
<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>Academic citations (APA · BibTeX · CFF)
APA citation
juliusbrussee. (2026). lean-build security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-lean-build/audits/1BibTeX citation
@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"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
Use $lean-build to implement [feature]. First state observable acceptance criteria and explicit non-goals from this repository.
Use $lean-build for [feature]. Trace the entry point and owning layers, then implement the smallest coherent path using existing patterns.
Use $lean-build to add [behavior]. Refactor only where direct patching would duplicate behavior, weaken ownership, or hide the root cause.
Use $lean-build to integrate [service]. Define lifecycle needs, material tradeoffs, focused verification, and the exact stop condition before implementation.
Best Practices
- 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.
Avoid
- 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.
Frequently Asked Questions
What types of work fit Lean Build?
Does the skill always choose the fewest changed files?
When does it recommend refactoring?
Will it add configuration for future flexibility?
How does it decide when to stop?
Does Lean Build replace broader testing?
Developer Details
Author
juliusbrusseeLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7b8c859294bb987ad70ef94d6499a7aa97cc8252
Maintenance freshness
8/13/2026
Usage
0 downloads · 0 views
File structure