What “recurring features” means
Recurring features are repeatable rolls of work driven by Markdown templates under something like docs/specs/recurring/ in your repo: each cycle can create or refresh specs, assign IDs, move lanes, and commit — so maintenance work (dependency sweeps, benchmark refresh, scheduled security passes tied to recurring, etc.) stays structured instead of ad-hoc.
That is separate from one-shot scheduling (aigon schedule), which fires a single kickoff at a wall time.
Related commands
| Capability | Command |
|---|---|
| One-shot deferred kickoffs, polled by the dashboard server | aigon schedule … |
| Cadence-driven template batches | aigon recurring-run / aigon recurring-list |
| On-demand repo scan | aigon security-scan |
Merge-gate scanning, manual security-scan, and automated weekly template runs all ship in Aigon itself — there is nothing extra to install.
Deleting one recurring instance
Deleting a generated recurring feature with aigon feature-delete <ID> skips that instance’s current week, month, or quarter. The dashboard server will not recreate it during the same cadence period, but the template remains enabled and can generate the next period normally. To stop future periods entirely, remove or disable the recurring template instead of deleting only its current instance.
See also
schedulecommand — one-shot deferred starts- Security scanning — merge gate and on-demand
security-scan