docs: subagent-driven workflow with knowledge base - #190
Merged
Conversation
- Delegate issue triage, implementation and code review to subagents - Issue triage scans ALL open issues (--limit 30 is only gh's default) - coder/review collect follow-up issue candidates and only create them after explicit user approval - Add docs/helpers/ knowledge base: faq.md, decisions.md, README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Rewrite
docs/workflow.mdso the whole issue cycle (triage, implementation, code review) is driven by Pi subagents, and add a persistent knowledge base indocs/helpers/.Changes
explore/delegate) scans ALL open issues —--limit 30is onlygh's default, use--limit 100or paginatecoder(orcoder-high/workerfor harder tasks)review(orreview-criticalfor risky changes), repeated until cleancoder/reviewcollect follow-up issue candidates and ask the user before creating them viagh issue create(never without approval)coder/reviewmaintain a knowledge base indocs/helpers/— FAQ, common mistakes and decisions (seeded with existing project pitfalls: tests: running run-tests.php deletes legacy tracked .php test files that share a basename with .phpt #187, tests: pre-installed zvec PHP extension (v0.4.10) shadows FFI classes — suite must run with -n #188, FFI memory, etc.)Testing
Docs-only change — no builds or tests required.
Code Review