awesome-loop-engineering / meta /DISCUSSIONS.md
cy0307's picture
Publish dataset mirror with resource sheet
549e098 verified
|
Raw
History Blame Contribute Delete
1.96 kB
# Discussion Guide
GitHub Discussions are enabled for this repository. Use them to gather examples, improve definitions, and keep resource curation transparent.
Seed thread: [Show your Loop Engineering patterns](https://github.com/ChaoYue0307/awesome-loop-engineering/discussions/2).
## Suggested Categories
- **Pattern Examples**: real or anonymized loop patterns with trigger, intake, state, verification, budget, and escalation.
- **Resource Suggestions**: candidate papers, blogs, docs, tools, benchmarks, critiques, or adjacent lists.
- **Definitions And Scope**: questions about what is or is not Loop Engineering.
- **Runtime Implementations**: Codex, Claude Code, GitHub Agentic Workflows, custom workflow engines, and related tooling.
- **Translations**: language-specific discussion and translation maintainers.
If GitHub's default categories are used, prefix discussion titles with the category name, such as `[Pattern Example] PR babysitter for docs-only repos`.
## Starter Discussion Prompts
### Pattern Examples
```text
What loop patterns are you using?
Please share the objective, trigger, intake, agent roles, verification gate, durable state, budget, escalation path, and receipts if public or anonymized.
```
### Definitions And Scope
```text
Where should the boundary between Harness Engineering and Loop Engineering sit?
Useful answers should include concrete examples and explain whether the system repeats, persists state, verifies, and decides next actions.
```
### Runtime Implementations
```text
Which runtime primitives make Loop Engineering easier?
Examples: schedules, goals, hooks, worktrees, skills, plugins, subagents, workflow state, traces, approvals, and dashboards.
```
## Moderation Standard
Discussions should follow `CODE_OF_CONDUCT.md`, preserve the repository's narrow AI/coding-agent scope, and avoid unsupported claims. Promotional posts should include concrete technical details or they may be closed.