Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work.
Run:
bd prime
If that prints nothing, check whether the repository has an active Beads workspace:
bd where
Use the bd CLI when shell access is available. It is the most compact and direct Beads interface.
bd ready
bd list --status=open
bd list --status=in_progress
bd show <id>
bd update <id> --claim
bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2
bd close <id> --reason="Completed"
Use Beads for:
Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state.
bd edit; it opens an interactive editor. Use bd update flags instead.--json when parsing bd output programmatically.bd prime may already be injected. Run it manually when context is missing.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Compare evaluated runs in a retort experiment along factor dimensions. Surfaces effects of each factor, aggregates across replicates, and highlights cells that diverge qualitatively — complementing (not replacing) retort's ANOVA analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Determine the TRUE cause of a failed retort run before attributing it. Ground-truth every failure (run its tests, read its agent logs, inspect its workspace) and classify it as an infrastructure false-fail, a genuine model miss, or an environment issue — never trust the gate verdict or a log signature alone. Use whenever a run is recorded failed (test_coverage=0 / gate fail), a pass rate looks low, or you're deciding whether a "failure" is real before reporting or proceeding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate a single retort experiment run. Score the generated code against the task's TASK.md requirements, run its build and tests, compute metrics, and emit a structured evaluation report plus a machine-readable findings file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Aggregate a retort run's findings.jsonl into a machine-readable assessment.json summary with severity counts, penalty score, requirement coverage, and top findings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize the architecture of code generated by a single retort run. Produces module-level structure, interfaces, and control flow in a form suitable for cross-run comparison — not a full codebase-summary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refresh the data tables in optimal-blog.md from master.db. Checks the data for integrity problems FIRST, then runs the generator that picks per-language winners and splices every GEN-marked table, then reconciles the surrounding prose. Use after new experiment results land, or when the optimal-blog numbers are stale.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.