技能潮 SkillTide 提交收录
官方说明开源项目7 天前
DraconDev/pi-goal-list-loop-audit

DraconDev/pi-goal-list-loop-audit

Long-running autonomy for Pi: draft goals, build projects from specs, run audited task queues, and recover interrupted work. Independent auditors verify completion.
在 GitHub 查看 ↗直链 · 无中转页
★ 数取值
27 ★ · DraconDev/pi-goal-list-loop-audit · 取自该仓库的 GitHub 页面 · (2026-10-16 20:00:20 核对)
来源明细
从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
收录与活跃
收录于 2026-10-10 · 最近见到 2026-10-14 · 共见到 2 次 · 被 1 个来源列出
评分构成
综合分 103 · 27 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 DraconDev/pi-goal-list-loop-audit;我们收录于 2026-10-10;最近见到 2026-10-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

pi-goal-list-loop-audit

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

> **Give Pi an outcome—not another prompt to stop halfway through.**
GLLA turns substantial work into a durable, supervised process: agree on the
finish line, keep working across turns, recover interruptions, and check the
result before calling it complete.
Then, in Pi:
Review the proposed objective and acceptance criteria, confirm them, and let
Pi work. Use /glla status to see what it is doing and what needs your attention.
**Waiting** yields to named background work while supervision remains active;
**paused** freezes automatic continuation. See waiting and recovery.
Install and update · Practical workflows ·
Recovery · Settings ·
Pi package catalog
About GLLA
Coding agents are good at taking the next step. Substantial projects need
something more: a remembered commitment, a reason to keep going, a way to
recover, and a finish line that does not depend on the agent sounding confident.
GLLA supplies that supervision inside Pi.
The main agent researches and implements; GLLA keeps the objective, progress,
pauses and completion claims on disk. A separate auditor inspects the result
against the agreed contract. Rejected claims return to work rather than becoming
successful-looking endings.
This is useful for features spanning several subsystems, migrations, repository
audits, documentation overhauls, backlogs and projects built from a specification.
It is not a new model, a hosted coding service, or a promise of hands-off correctness.
It works with your Pi session, tools and authenticated providers.
**The ambition is less babysitting, not less accountability.** You choose the
outcome and permissions; the agent handles ordinary implementation decisions;
important scope changes and decisions remain visible. Durable state and evidence
make it easier to inspect what happened—even after a long run or interruption.
Pick the right work shape
| You want… | Use | What counts as finished |
|---|---|---|
| One result: a fix, feature, migration, research report or audit | /goal | An accepted completion audit against the objective and contract |
| Several independently verifiable results | /list | Each item is audited separately; the queue advances after settlement |
| Repeated improvement | /loop | A configured bound, metric plateau or explicit stop—not a claim that everything is solved |
| A project built toward an evolving specification | /loop respec | Every adopted requirement independently verified and the project archived |
For a quick question or tiny edit, ordinary Pi chat is usually enough. Use GLLA
when continuity and verification are worth the extra model calls and coordination.
Start with one goal
A rough request can become a confirmed plan:
GLLA drafts the outcome, asks questions when needed and offers confirmation.
Bare /goal opens the interview; /goal plan ... requests research-first drafting.
You do not need to arrive with a perfect specification.
If you already know the finish line, a Done when: contract starts directly:
/goal start ... explicitly skips drafting. Be deliberate: an explicit start
can replace existing work. Drafting and direct starts are different consent paths.
The work cycle
1. **Agree:** preserve the objective and observable acceptance criteria.
2. **Build:** the agent researches, plans and implements across supervised turns.
3. **Recover:** retain work and use bounded recovery when providers, sessions or workers fail.
4. **Claim:** the agent submits evidence; saying “done” in chat does not close the goal.
5. **Audit:** a detached verifier checks the saved claim. Missing evidence or rejection keeps work open.
6. **Archive:** accepted, durably settled work leaves a result and evidence record.
The agent can propose a task plan with propose_task_list; confirming the plan
makes its tasks tracked milestones, not proof of correctness. Completion claims
with unfinished tasks are refused unless an explicit deferral was recorded.
Controls you will actually use
| Command | Purpose |
|---|---|
| /glla status | Inspect supervision, recovery and current work |
| /goal status | Inspect the saved goal |
| /glla pause | Freeze automatic supervision without killing an already running tool |
来源
github · https://github.com/DraconDev/pi-goal-list-loop-audit
按领域浏览
开源项目
Traction
27 ★
收录于
3 天前

更多开源项目

查看开源项目全部 731 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引