📦

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 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の 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

juliusbrussee のその他のスキル

すべて表示

📦

caveman-review

簡潔なプルリクエストレビューコメントを書く

プルリクエストレビューは、すぐに対応するには冗長になりがちです。このスキルは、フィードバックを場所、問題、修正を含む簡潔でそのまま貼り付けられるコメントとして整形します。

コーディング＆開発表示

📦

verify-and-stop

Verify Acceptance Criteria and Stop

Verification tasks often expand beyond their acceptance criteria. This skill selects sufficient checks, reports exact outcomes, and stops when proof is complete.

コーディング＆開発表示

📦