ken/opencode-boilerplate
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: autonomous setup flow and per-feature doc reconciliation

Browse Source 
- setup-project: run end-to-end without pausing for human approval between steps
- add-feature Step 8: reconcile all six persistent docs with each implemented feature
- AGENTS.md: align document-management principles with the new sync rule
- opencode.json: simplify permission config
This commit is contained in:
Ken Yasue
2026-06-28 18:29:48 +02:00
parent ced279e2df
commit e1ef10be6e
4 changed files with 24 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.opencode/command/add-feature.md
View File

@ -114,9 +114,18 @@ If any of the following situations occur while the implementation loop is runnin
- Lessons learned
- Improvement suggestions for next time
2. Determine whether this change affects the project's fundamental design or architecture.
2. **Reconcile all six persistent documents in `docs/` with the feature just implemented.** For each document, read its current content, then use the edit tool to update it so it reflects the new feature. An update may be skipped **only** when the document genuinely requires no change for this feature — in that case, leave the document untouched and note the skip reason in the retrospective.
3. If there is an impact, use the edit tool to update the relevant persistent documents in `docs/`.
- ✅ `docs/product-requirements.md` — add/update user stories, acceptance criteria, non-functional requirements, and success metrics for the feature
- ✅ `docs/functional-design.md` — add/update functional modules, screens, data flows, and state changes introduced by the feature
- ✅ `docs/architecture.md` — add/update components, layers, data models, APIs, and non-functional decisions affected by the feature
- ✅ `docs/repository-structure.md` — add/update any new directories, files, or modules created for the feature
- ✅ `docs/development-guidelines.md` — add/update any new conventions, patterns, or standards established during the feature
- ✅ `docs/glossary.md` — add/update any new domain terms introduced by the feature
3. **Consistency check**: re-read each updated document and confirm it is consistent with the other documents and with the implemented code. Fix any inconsistencies found.
4. **Once this step completes successfully, never stop; immediately proceed to the Completion Criteria.**
## Completion Criteria
@ -124,6 +133,6 @@ This workflow completes automatically once all of the following conditions are m
- Step 5: All tasks in `tasklist.md` are complete (`[x]` or skipped for a valid reason).
- Step 6: The `implementation-validator` subagent's validation passes.
- Step 7: The `test`, `lint`, and `typecheck` commands all succeed without errors.
- Step 8: Handover notes are recorded in `tasklist.md`.
- Step 8: Handover notes are recorded in `tasklist.md`, and all six persistent documents in `docs/` have been reconciled with the feature (updates applied, or a skip reason noted for each).
Until these completion criteria are met, continue to think autonomously, solve problems, and carry on the work.