스킬 lean-build

📦

lean-build

Name: lean-build
Author: juliusbrussee

콘텐츠 리비전 r1 안전

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.

지원: Claude Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

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.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/juliusbrussee-lean-build.md 서명된 manifest GET /api/skills/juliusbrussee-lean-build/manifest 서명된 lockfile GET /api/skills/juliusbrussee-lean-build/lockfile

테스트해 보기

"lean-build" 사용 중입니다. Add saved filters to the issue list without introducing new configuration.

예상 결과:

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

"lean-build" 사용 중입니다. Connect the current notification flow to a second provider.

예상 결과:

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.

"lean-build" 사용 중입니다. Fix duplicate status updates appearing in two interface views.

예상 결과:

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

보안 감사

안전

v1 • 2026. 8. 12. 버전별 보고서 열기

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

스캔된 파일

분석된 줄 수

검토 항목

오탐 무시됨

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

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

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)

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>

임베드 카드

<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>

학술 인용 (APA · BibTeX · CFF)

APA 인용

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

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"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

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.

이 프롬프트를 사용해 보세요

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.

모범 사례

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.

피하기

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.

자주 묻는 질문

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.

개발자 세부 정보

작성자

juliusbrussee

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

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

참조

7b8c859294bb987ad70ef94d6499a7aa97cc8252

유지보수 최신성

2026. 8. 13.

사용량

0 다운로드 · 0 조회

파일 구조

📁 agents/

📄 openai.yaml

📄 SKILL.md