fft coder ops
- Repo stars 0
- Author repo nano-core
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# FFT Coder Ops
Use this skill when handling coding delegation operations in FFT_nano.
## When to use this skill
- Use for `/coder` and `/coder-plan` delegation 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 agent`
- `use 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 agent`
- `use your coding agent skill`
## Validation Checklist
- Non-main `/coder` is rejected with safety message.
- Main `/coder` triggers delegation run start message.
- Main `/coder-plan` triggers plan run start message.
- Existing Telegram delegation safety rules remain unchanged.
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Delegation Triggers → Chat Safety Rules → Runtime Expectations
terms -> Use this skill when handling coding delegation operations in FFTnano. · - Use for /coder and /coder-plan delegation workflows. · - Do not use for non-coding tasks or normal chat replies. · - Never run destructive git commands unless explicitly requested. · Natural-language coding requests without explicit trigger must not auto-delegate. · - Delegation is only available in main/admin chat. · - Execute mode delegates once and returns delegated outcome. · - Non-main /coder is rejected with safety message.
files/cmd -> /coder · /coder-plan · /coder <task> · use coding agent · use your coding agent skill · /coder-plan <task> · coder-<timestamp>-<suffix>
body sha256 -> 8c2b6f38b837
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 skillExplicit plan-only: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.