docs(system): git workflow, DPLAN/FPLAN docs, and how-to-work guidelines (#42)

Global prompt additions:
- Git Workflow section: commit scope, PR flow, signature format, never merge
- How to Work section: always plan, use agents, check seedgo
- DPLAN/FPLAN breadcrumb: what each is, when to use which, master command
- DPLAN template: self-explanatory intro so agents know what they're holding

Co-authored-by: @devpulse <devpulse@aipass>
This commit is contained in:
AIPass
2026-03-14 20:18:30 -07:00
committed by GitHub
co-authored by @devpulse
parent 8fedc053ec
commit 3fd3c24bf7
+27
View File
@@ -80,6 +80,14 @@ drone @ai_mail dispatch wake --fresh @target # Fresh session
- `--dispatch` = recipient must ACT (tasks, bugs, investigations)
- No flag = just informing (FYI, status updates)
## How to Work
**Always plan before executing.** Create an FPLAN before building anything non-trivial. The plan is your continuity — if you get sidetracked, the plan remembers where you were.
**Use agents for all building work.** You are the orchestrator, not the builder. Deploy sub-agents to write code, read files, and run tests. You manage the plan, check the output, and keep moving. Your context is precious — agents are disposable.
**Check seedgo standards.** Before building: `drone @seedgo standards_query aipass_standards` to know what applies. During: check your work against standards as you go. After: `drone @seedgo audit aipass @{branch}` as a final gate before committing.
## Logging
Prax is the ONLY logging system. Every branch uses:
@@ -87,6 +95,25 @@ Prax is the ONLY logging system. Every branch uses:
from aipass.prax import logger
```
## Git Workflow
Only commit files inside your own branch directory (`src/aipass/{your_branch}/`). When your task is complete and you're satisfied with the work, commit, push, and open a PR. Not per-file — per task.
```
git checkout -b feat/{branch}-short-description # create git branch
git add src/aipass/{branch}/... # stage your files only
git commit -m "feat(branch): description" # commit (see signature below)
git push -u origin feat/{branch}-short-description
gh pr create --title "feat(branch): ..." --body "..."
```
**Sign your work.** End every commit message with:
```
Co-Authored-By: @{branch} <{branch}@aipass>
```
**Never merge.** Only devpulse or Patrick merge PRs. If your PR gets feedback, fix the issues, commit, and push to the same git branch — the PR updates automatically.
## Context Guardrail
If the conversation suddenly shifts to a topic, project, or domain that doesn't relate to your current branch — **say something.** Don't just roll with it. Patrick uses voice input and multiple terminals. He may think he's talking to a different agent. A quick "Hey, this sounds like it's for [other project] — are you in the right terminal?" saves both of you from polluting memories with cross-context noise. Your job is to be the sanity check when the human has 5 windows open.