Building with BACKS
This skill closes a recurring failure: a good patch in the wrong checkout or a
green test that never reaches the operator's app. The destination is the human's
requested product and path. Discover the target before writing.
Existing BACKS Build Flow task packet में जुड़ें; direct
invocation उसे एक बार बनाता है। एक integration owner रखें और established operator
essence/context reuse करें। task_mode मानें और bounded-loops
की deadline तथा remaining allowances workers, models और handoffs में साथ रखें। नया path
तय करने से budget restart या deployment authorization नहीं मिलती।
- Resolve the destination. Use the exact path named by the human. If none was
named, inspect the active workspace, recent project references, and repository
map. Do not substitute a nearby clone merely because it has a matching name.
इस skill की directory से
python scripts/resolve_target.py --repo <path> --target <file-or-directory> चलाएँ;
add --expected-root <path> when the human named the checkout. The command
returns nonzero for a missing target root, a path outside that root, or a
checkout mismatch or missing Git revision. A new target file may not exist
yet; its parent must. For a specifically named non-Git project, add
--allow-non-git and record that no revision is available.
- Pin the starting truth. Record the resolved root, branch or detached HEAD,
base_sha, current candidate_sha, worktree status, requested target,
app/service entry point और checks दर्ज करें। Commits होने पर original base pinned
रखें; candidate identity स्पष्ट अपडेट करें और pending paths फिर जाँचें।
Preserve unrelated edits. If another checkout is newer, compare revisions and
actual working trees before choosing; "newest" is a measured claim.
- Map the route. Trace user action to entry point, implementation, data,
outputs, and deployment seam. Name the existing owner of the behavior and
any dependent consumers. Use
repo-map, architecture-engineer, and
root-cause-first when those seams are uncertain.
- Build in the resolved place. Give parallel readers distinct questions and
writers non-overlapping files or isolated worktrees. Keep one integration
owner. Failure class बंद करने वाला smallest change करें; defect में current
workflow के अंदर
repair-loop लें। चुना या explicit request हो तो full elite-build
play अपनाएँ, valid stages reuse करते हुए, फिर boot किए बिना। Review/diagnosis edits
के बिना findings लौटाता है।
- Path साबित करें। Current sealed RED → minimal fix → sniper lint/type/test
checks → clean-code-gauntlet loop अपनाएँ। Pinned aggregate candidate diff से scope
लें; repo की real commands चलाएँ और missing/N/A checks ईमानदारी से बताएँ। Author-
disjoint review और required full affected-suite landing pass बनाए रखें। Requested
scope में actual app/CLI surface और runtime logs देखें। Deployed source का exact
revision/hash और observed behavior लिखें; जो exercise न हो सका वह बताएँ।
- Promote through the project's own route. Read its deployment instructions
and approval rules from that repository. Never transplant a deployment
command from another project. Re-run the target check before installation
and verify the running process uses the installed code afterward.
If the destination remains ambiguous, keep read-only investigation moving and
ask for the missing path only after checking available evidence. Never claim a
cross-host installation merely because files were copied; verify discovery in
each host or mark it unverified.
Allowance समाप्त हो तो verified target, candidate, unresolved evidence और exact next
action के साथ STILL-BUILDING checkpoint करें। Original mission limits बचाएँ;
exhausted allowance खर्च किए बिना उपयोगी authorized work पूरा करें। Local check माँगी
गई delivery evidence की जगह नहीं लेता।
1---2name: building-with-backs-53description: "BACKS project build/repair, wrong-folder या checkout ambiguity सुलझाने, या authorized change IDE से actual runtime तक ले जाने में उपयोग करें।"4license: MIT5metadata:6 source: https://skillmd.com/skills/tcuzzo/building-with-backs-57---89# Building with BACKS1011This skill closes a recurring failure: a good patch in the wrong checkout or a12green test that never reaches the operator's app. The destination is the human's13requested product and path. Discover the target before writing.1415Existing [BACKS Build Flow](../backs-build-flow/SKILL.md) task packet में जुड़ें; direct16invocation उसे एक बार बनाता है। एक integration owner रखें और established operator17essence/context reuse करें। `task_mode` मानें और [bounded-loops](../bounded-loops/SKILL.md)18की deadline तथा remaining allowances workers, models और handoffs में साथ रखें। नया path19तय करने से budget restart या deployment authorization नहीं मिलती।20211. **Resolve the destination.** Use the exact path named by the human. If none was22 named, inspect the active workspace, recent project references, and repository23 map. Do not substitute a nearby clone merely because it has a matching name.24 इस skill की directory से25 `python scripts/resolve_target.py --repo <path> --target <file-or-directory>` चलाएँ;26 add `--expected-root <path>` when the human named the checkout. The command27 returns nonzero for a missing target root, a path outside that root, or a28 checkout mismatch or missing Git revision. A new target file may not exist29 yet; its parent must. For a specifically named non-Git project, add30 `--allow-non-git` and record that no revision is available.312. **Pin the starting truth.** Record the resolved root, branch or detached HEAD,32 `base_sha`, current `candidate_sha`, worktree status, requested target,33 app/service entry point और checks दर्ज करें। Commits होने पर original base pinned34 रखें; candidate identity स्पष्ट अपडेट करें और pending paths फिर जाँचें।35 Preserve unrelated edits. If another checkout is newer, compare revisions and36 actual working trees before choosing; "newest" is a measured claim.373. **Map the route.** Trace user action to entry point, implementation, data,38 outputs, and deployment seam. Name the existing owner of the behavior and39 any dependent consumers. Use `repo-map`, `architecture-engineer`, and40 `root-cause-first` when those seams are uncertain.414. **Build in the resolved place.** Give parallel readers distinct questions and42 writers non-overlapping files or isolated worktrees. Keep one integration43 owner. Failure class बंद करने वाला smallest change करें; defect में current44 workflow के अंदर `repair-loop` लें। चुना या explicit request हो तो full `elite-build`45 play अपनाएँ, valid stages reuse करते हुए, फिर boot किए बिना। Review/diagnosis edits46 के बिना findings लौटाता है।475. **Path साबित करें।** Current sealed RED → minimal fix → sniper lint/type/test48 checks → clean-code-gauntlet loop अपनाएँ। Pinned aggregate candidate diff से scope49 लें; repo की real commands चलाएँ और missing/N/A checks ईमानदारी से बताएँ। Author-50 disjoint review और required full affected-suite landing pass बनाए रखें। Requested51 scope में actual app/CLI surface और runtime logs देखें। Deployed source का exact52 revision/hash और observed behavior लिखें; जो exercise न हो सका वह बताएँ।536. **Promote through the project's own route.** Read its deployment instructions54 and approval rules from that repository. Never transplant a deployment55 command from another project. Re-run the target check before installation56 and verify the running process uses the installed code afterward.5758If the destination remains ambiguous, keep read-only investigation moving and59ask for the missing path only after checking available evidence. Never claim a60cross-host installation merely because files were copied; verify discovery in61each host or mark it unverified.6263Allowance समाप्त हो तो verified target, candidate, unresolved evidence और exact next64 action के साथ **STILL-BUILDING** checkpoint करें। Original mission limits बचाएँ;65exhausted allowance खर्च किए बिना उपयोगी authorized work पूरा करें। Local check माँगी66गई delivery evidence की जगह नहीं लेता।