Complete TEGWICK-WP-0002 personal project intake scaffold

Establish the capture-to-commitment pipeline with INTAKE.md, structured
agent-tasks/ and decisions/ layouts, and seed the first prioritized
workstream (TEGWICK-WP-0003 Binky critical path visibility).
This commit is contained in:
2026-06-24 15:25:54 +02:00
parent 4295d00d9a
commit d4080de393
13 changed files with 566 additions and 11 deletions

82
agent-tasks/README.md Normal file
View File

@@ -0,0 +1,82 @@
# Agent Tasks
Bounded, approval-aware prompts for agents working in `tegwick-control`.
## When to use
Create an agent task when:
- the work stays inside this repository (drafting, structuring, summarizing);
- boundaries and forbidden changes are clear;
- human approval gates are explicit;
- the task is ready to hand to an agent without further triage.
Do **not** use agent tasks for:
- implementation work in other repos (prepare the prompt here, execute elsewhere);
- legal, tax, or financial conclusions;
- converting options into commitments without approval.
## Layout
```text
agent-tasks/
├── README.md this file
├── <area>-<action>-<subject>.md ready agent prompts
└── archive/ completed or superseded tasks
```
Flat layout by default. Move finished tasks to `archive/` during review.
## Naming
```text
<area>-<action>-<subject>.md
```
| Segment | Examples |
|---|---|
| area | `tegwick`, `binky`, `helix`, `coulomb` |
| action | `review`, `surface`, `draft`, `classify` |
| subject | `critical-path`, `area-cards`, `migration-slice` |
Examples:
- `binky-surface-critical-path.md`
- `tegwick-review-area-cards.md`
## File format
Copy `templates/agent-task.md` and fill every section. Required sections:
- Goal
- Context
- Allowed Changes
- Forbidden Changes
- Expected Output
- Acceptance Criteria
- Human Approval Required For
## Lifecycle
| State | Meaning | Location |
|---|---|---|
| Seed | Bootstrap or historical reference | root or `archive/` |
| Ready | Approved for agent execution | root |
| Done | Completed; move to `archive/` | `archive/` |
Track state in the task file header:
```markdown
Status: ready | done | superseded
Workplan: TEGWICK-WP-NNNN (if linked)
Area: binky | tegwick | helix | ...
```
## Intake path
```text
inbox/ → triage (INTAKE.md) → agent-tasks/ → agent session → archive/
```
See `INTAKE.md` for the full pipeline.

View File

View File

@@ -0,0 +1,72 @@
# Agent Task: Surface Binky critical path
Status: ready
Workplan: TEGWICK-WP-0003
Area: binky
## Goal
Populate `areas/binky-company.md` with an initial critical-path view: open
obligations, survival risks, business model options, and the next visible
surfaces — without making legal, tax, or financial conclusions.
## Context
Binky is A3 Critical in `PROJECT_LANDSCAPE.md`. The area card is still seed
content. TEGWICK-WP-0003 breaks visibility work into structured tasks. This
agent task covers the drafting pass across T01T03.
Human must supply or confirm factual details (dates, amounts, filing status).
Use `[NEEDS HUMAN INPUT]` markers where facts are unknown.
## Inputs
- `areas/binky-company.md`
- `PROJECT_LANDSCAPE.md`
- `WORKPLAN.md` (Phase 2)
- `workplans/TEGWICK-WP-0003-binky-critical-path.md`
- `INTAKE.md`, `AGENT_RULES.md`
## Allowed Changes
The agent may:
- edit `areas/binky-company.md` (Current State, Commitments, Options, Risks,
Open Decisions, Next Surface);
- add clearly marked placeholders for unknown facts;
- propose draft entries for `TASKS.md` (T04, T05) as commented suggestions in
the area card, not as live commitments.
## Forbidden Changes
The agent must not:
- state legal, tax, or accounting conclusions as facts;
- create payment, filing, or contract instructions;
- add secrets, credentials, or private account data;
- mark items as commitments in `TASKS.md` without explicit human approval;
- change Binky's activation level;
- create or modify other repositories.
## Expected Output
Updated `areas/binky-company.md` containing:
1. **Open obligations** — legal, tax, accounting (with unknowns marked).
2. **Survival risks** — ranked by urgency where possible.
3. **Business model options** — separated from commitments.
4. **Next surface** — what human review should tackle first.
## Acceptance Criteria
- Area card is no longer generic seed text in the critical-path sections.
- Options and commitments are clearly separated.
- No item is presented as resolved fact without source or human confirmation.
- TEGWICK-WP-0003 T01T03 can be marked done after human review of the draft.
## Human Approval Required For
- Converting any draft item into a `TASKS.md` commitment;
- Changing activation level;
- Any statement presented as legal, tax, or financial fact;
- Contacting advisors, authorities, or third parties.