使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-ledger開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
ds-ledger
A long run forgets its own reasons. A short written ledger keeps the goal in view and lets a reviewer trust the result.
Steps
- Create one TSV file, for example
.ds-ledger.tsv, with the headerts phase decision why evidence result. Put the goal and done condition in the first row. - Before each step, re-read the goal row and the last ten rows. Check that the next step still serves the goal. If it does not, log the drift and correct course.
- After each real decision, append one row:
- ts: ISO 8601 time.
- phase: the phase or workstream.
- decision: what you chose or did, one line.
- why: the reason in plain words.
- evidence: a pointer, never prose. A commit hash,
file:line, a command and its result, or an artifact path. - result: the outcome, such as "tests pass", "reverted", "open".
- Keep each cell on one line with no tabs.
- Log reverts and dropped work too, with the reason. Failures are the most useful rows.
- At the end, add a summary row and point the user to the file. Commit it only if a reviewer needs it.
Stop when
- The run ends and the summary row is written.
- If three rows in a row show no progress toward the goal, stop the run and report.
Rules
- Every row needs evidence you can open or rerun. "Looked fine" is not evidence.
- Write rows the way you would tell a teammate, plain and concrete.
- Do not rewrite old rows. Append corrections.
