den-ree/blanche-skills

bindify

Use when the user references wip-docs/, .bindify/, bindify commands, plan/proposal/update/verify artifacts, coordinator workflows, multi-agent execution with shared markdown state, iterate-planning-mode, prototype-mode, verify-worktree, drafting a brief, in…

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/den-ree/blanche-skills --skill bindify

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Bindify

Filesystem protocol for AI agents on software work. Active plan docs live in wip-docs/<feature>/<plan>/ at the project root. The tracking repo (.bindify/ or bindify/) holds architecture, migrated plans, and history/.

Load command and template files from this skill's references/ on demand. Layout detail: references/docs/layout.md. Pipeline diagrams: references/docs/workflow.md.

Three path layers

LayerWhereUse
SkillThis installCommands + templates
Active WIPwip-docs/<feature>/<plan>/Write brief/proposal/plan/updates/verify. Coordinator at wip-docs/<feature>/coordinator.md
Tracking.bindify/ or bindify/Read project/architecture; migrate development/ at packaging; history may start at draft PR

Never open tracking looking for skill commands or templates.

Read by role

RoleRead
Plannerworking-style.md, draft-brief, generate-proposal, save-agent-plan, publish-plan (branch stack), wait for ready
Executorworking-style.md, iterate-planning-mode, summarize-work-for-updates, next_step.py, generate-verify on finish
Reviewerreview-plan (build/CI gate + one fixes round)
Packagerlog-pr, publish-bindify-pr, generate-history-summary

When to invoke each command

User signalCommandReference
adapt / configure projectconfigure-projectreferences/commands/configure-project.md
coordinate updatescoordinate-updatesreferences/commands/coordinate-updates.md
capture briefdraft-briefreferences/commands/draft-brief.md
generate proposalgenerate-proposalreferences/commands/generate-proposal.md
save plan / proposal approvedsave-agent-planreferences/commands/save-agent-plan.md
/bindify / publish planpublish-planreferences/commands/publish-plan.md
run step / iterateiterate-planning-modereferences/commands/iterate-planning-mode.md
review open plan PRreview-planreferences/commands/review-plan.md
prototypeprototype-modereferences/commands/prototype-mode.md
verify worktree (macOS)verify-worktreereferences/commands/verify-worktree.md
after a stepsummarize-work-for-updatesreferences/commands/summarize-work-for-updates.md
scan architecturescan-architecturereferences/commands/scan-architecture.md
log PRlog-prreferences/commands/log-pr.md
history summary / abandonedgenerate-history-summaryreferences/commands/generate-history-summary.md
regenerate overviewregenerate-overviewreferences/commands/regenerate-overview.md
publish bindify PR / packagepublish-bindify-prreferences/commands/publish-bindify-pr.md
generate verifygenerate-verifyreferences/commands/generate-verify.md
investigate / prior fixesinvestigatereferences/commands/investigate.md
research codebaseresearch-codebasereferences/commands/research-codebase.md
repair linksupdate-linksreferences/commands/update-links.md
log hotfixlog-hotfixreferences/commands/log-hotfix.md
abandon / drop planabandon-planreferences/commands/abandon-plan.md

Hard rules

  • Active docs stay in wip-docs/<feature>/<plan>/ until packaging. Coordinator is wip-docs/<feature>/coordinator.md. Several plans of one feature can sit side by side. Read sibling plan docs before writing a proposal or plan, and again before a step. Do not write active plan artifacts into tracking development/ during apply. Flat files directly in wip-docs/ mean stop and ask.
  • Branch stack: see publish-plan.md. A different plan, while on another plan or plan-fixes branch of the same feature, is cut from the current tip. Its draft PR still targets feature/<feature-slug>. Merge that PR with a merge commit. Executors never create branches. Only review-plan creates plan-fixes/.
  • One history card per plan. Slug is <feature-slug>-<plan-slug>. Iterations and plan-fixes refresh that card.
  • Packaging migrates and deletes that plan folder only. The feature folder goes away when no plan folders remain.
  • Never modify existing plan steps during apply. Execution state → updates.md. review-plan may append steps on plan-fixes/ only.
  • Every update entry needs Impact & Connections + Architecture. Append-only for updates.md and hotfixes.md.
  • Architecture Responsibility is human-owned. scan-architecture fill appends change-log lines and edges only — and runs at packaging, not per step.
  • Package per plan on the plan head after sign-off, before the plan PR merges into its base. Feature → main is human, outside bindify. History merged = plan PR into its base.
  • Brief ≤ 150 words. Proposal: Primer ≤ 300 words (+ table); Risks ≤ 3 bullets. Primer teaches the technology; project choices are facts in In this project.
  • Prototype-first for user-facing features; Prototype steps carry a human checkpoint.
  • Repo-relative paths only. No code dumps in context files.
  • Investigate tracking names/fixes before product code. Clarify before brief.md.
  • Chat is caveman; artifacts stay normal prose. Plan/build with ponytail (references/docs/working-style.md).
  • Blanche owns agent PRs: commits --author="blanche <blanche@bindify.app>"; gh pr create via blanche_gh_token.py so author is blanche[bot]. Missing credentials → stop. See references/docs/blanche-github-app.md.
  • update-links runs at generate-verify and at migration (plus history/hotfix/architecture writes) — not after every WIP write.

Two responsibilities

PhaseDocumentWho
plan / propose / reviewbrief → proposalhuman + AI
applyplan + updatesexecutor via iterate
verifyverify.mdhuman checklist
reviewready plan PRreviewer via review-plan
packagemigrate + historypackager
abandonhistory abandonedhuman-triggered abandon-plan

What to read next

  • references/AGENTS.md — drop-in entry for host repos
  • references/docs/working-style.md — clarify, caveman, ponytail
  • references/docs/workflow.md — branch stack visuals, roles
  • references/docs/layout.md — folder trees
  • references/docs/blanche-github-app.md — App token setup
  • references/commands/<name>.md — load before invoking
  • references/templates/<name>.md — when creating artifacts

When invoking a command, read that command file first.