FFT Coder Ops
Use this skill when handling coding delegation operations in FFT_nano.
When to use this skill
- Use for
/coderand/coder-plandelegation workflows. - Use when enforcing main/admin chat boundaries for coding execution.
- Use when tracking delegated run IDs and progress-stream behavior.
When not to use this skill
- Do not use for non-coding tasks or normal chat replies.
- Do not use when no explicit delegation trigger is present.
- Do not use in non-main chats for delegated execution.
Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Never bypass main-chat-only coder delegation safety rules.
- Do not add automatic delegation; delegation remains explicit trigger-based.
Delegation Triggers
Explicit execute:
/coder <task>use coding agentuse your coding agent skill
Explicit plan-only:
/coder-plan <task>
Natural-language coding requests without explicit trigger must not auto-delegate.
Chat Safety Rules
- Delegation is only available in main/admin chat.
- Non-main chats may request coding help, but must be handled directly or rejected for delegation.
- Scheduled tasks must not trigger coder delegation.
Runtime Expectations
- Execute mode delegates once and returns delegated outcome.
- Plan mode returns implementation/test plan without direct edits in outer orchestrator turn.
- Delegation run IDs are generated (
coder-<timestamp>-<suffix>) and surfaced in progress messages. - Progress streaming should avoid final duplicate full-message sends.
Operator Commands
Main Telegram chat commands:
/coder <task>/coder-plan <task>
Alias phrases in main chat:
use coding agentuse your coding agent skill
Validation Checklist
- Non-main
/coderis rejected with safety message. - Main
/codertriggers delegation run start message. - Main
/coder-plantriggers plan run start message. - Existing Telegram delegation safety rules remain unchanged.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.