ashokraj2011/singularityflow
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Singularity Flow runs a governed software development lifecycle out of Git itself. Work items move through declared phases; every artifact and every approval is a commit, so any machine can pick the...
개요
Singularity Flow runs a governed software development lifecycle out of Git itself. Work items move through declared phases; every artifact and every approval is a commit, so any machine can pick the work up from the repository alone. Eight seconds, entirely offline, no model invoked, and your own repository is untouched — it builds a throwaway one, takes a work item through every governed step, and removes it. It is the fastest way to see what the rest of this document describes. Before a POC demo, run npm run poc:release-gate. It builds diagnostic local artifacts and proves the seeded POC workflow against a throwaway real Git remote, independent reviewer, native Copilot handoff, and restart recovery without invoking a model. It is not release authority; a release candidate uses the retained build-once artifact pair and signed physical-host matrix described in docs/RELEASE-ARTIFACT-HANDOFF.md.
README
원문 README의 일부입니다. 원문 보기.
Singularity Flow 0.9.0
Singularity Flow runs a software development lifecycle out of Git itself. Work items move through declared phases; every artifact and every approval is a commit, so any machine can pick the work up from the repository alone.
Start here
singularity-flow quickstart
Eight seconds, entirely offline, no model invoked, and your own repository is untouched — it builds a throwaway one, takes a work item through every step, and removes it. It is the fastest way to see what the rest of this document describes.
Before a POC demo, run npm run poc:release-gate. It builds diagnostic local artifacts and proves
the seeded POC workflow against a throwaway real Git remote, independent reviewer, native Copilot
handoff, and restart recovery without invoking a model. It is not release authority; a release
candidate uses the retained build-once artifact pair and signed physical-host matrix described in
docs/RELEASE-ARTIFACT-HANDOFF.md. See
the verification checklist for the evidence boundary and the
Playwright POC runbook for real-machine host setup, authorized
target smoke testing, evidence capture, and day-of-demo rehearsal.
Then, on a repository you care about:
| You want to | Run |
|---|---|
| Set up a repository you already have | singularity-flow init |
| Set up a new capability, with its configuration branch and ledger | singularity-flow bootstrap |
| Get one personalized, read-only recommendation | singularity-flow recommend |
| Track a personal outcome across work | singularity-flow goal create "" --success "" |
| Promote an outcome into a durable execution plan | singularity-flow goal govern then singularity-flow goal plan |
| Review private local return memory | sflow journal today / sflow journal refresh |
| Execute or inspect the next step | singularity-flow next / singularity-flow nextsteps WORK-123 |
| Orient yourself or return to a Story without changing state | sflow home / sflow story return WORK-123 |
| Land a small change without creating a Story first | singularity-flow adhoc start / singularity-flow land |
| Create and audit a signed deliverable without a product repository | singularity-flow local start / singularity-flow local audit |
| See what a command does, with examples | singularity-flow --help |
init deliberately asks no organisation question and writes no capability map. Until a reviewed
map is activated, the repository is the single implicit capability This repository
(repository-root). Start the first Story normally. Add structure later only when a narrower owner,
protected path, or published dependency is real; see
Progressive capability disclosure.
The full documentation map is in docs/README.md.
추천 도구
다른 키워드를 입력하거나 필터를 제거해 보세요.
설치
npx skillfish add ashokraj2011/singularityflow