| 1 | --- |
| 2 | configured: false |
| 3 | interval: 10 |
| 4 | timeout: 30 |
| 5 | description: "My squad work loop" |
| 6 | --- |
| 7 | |
| 8 | # Squad Work Loop |
| 9 | |
| 10 | > ⚠️ Set `configured: true` in the frontmatter above to activate this loop. |
| 11 | > Run with: `squad loop` |
| 12 | |
| 13 | ## What to do each cycle |
| 14 | |
| 15 | Describe what your squad should do every time the loop wakes up. Be specific — |
| 16 | the more context you give, the better your squad performs. |
| 17 | |
| 18 | Examples: |
| 19 | - Check for new messages in a Teams channel and summarize action items |
| 20 | - Review recent pull requests and flag anything needing attention |
| 21 | - Run a health check on staging and report anomalies |
| 22 | - Scan the inbox for anything that needs a response today |
| 23 | |
| 24 | <!-- Replace this section with your actual loop instructions. --> |
| 25 | |
| 26 | ## Monitoring (optional) |
| 27 | |
| 28 | If you want your squad to watch external channels, enable monitor capabilities: |
| 29 | |
| 30 | ```bash |
| 31 | squad loop --monitor-email --monitor-teams |
| 32 | ``` |
| 33 | |
| 34 | ## Personality (optional) |
| 35 | |
| 36 | If your squad has a specific voice or style, describe it here so each cycle |
| 37 | stays consistent. |
| 38 | |
| 39 | Example: "Be concise. Use bullet points. Flag blockers clearly." |
| 40 | |
| 41 | ## Tips |
| 42 | |
| 43 | - **Be specific.** Vague prompts produce vague results. |
| 44 | - **Set boundaries.** Tell the squad what NOT to do (e.g., "Don't send messages to anyone but me"). |
| 45 | - **Start small.** Begin with one task per cycle, then expand. |
| 46 | - **Use frontmatter.** `interval` controls how often the loop runs. `timeout` caps each cycle. |