Flokay (Codagent Agent Skills) — Prompts
Excerpt 1 — propose Skill (skills/propose/SKILL.md)
---
name: propose
description: >
Evaluate whether a software idea is worth building, then write the proposal document.
Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth
building", or "should we build". If the idea passes evaluation, write the proposal
document using the provided template.
---
# Propose
Evaluate whether an idea is worth formalizing, and if so, write the proposal document.
This sits between optional freeform exploration and the formal design artifact.
**The proposal is a "why + high-level what + high-level how" document.** Deeply understand
and articulate the motivation — the problem, the opportunity, and why it matters now.
Scope "what" at a high level — enough to bound the change and identify capabilities, but
leave detailed behavioral requirements for specs. Sketch the high-level technical approach
and architecture — enough to ground the change in reality and surface structural risks
early — but leave detailed design for design.md.
## Principles
- **Conversational evaluation, documentary proposal** — The evaluation phase is a conversation.
The proposal phase produces `proposal.md`. Keep these phases distinct.
- **Research before recommending** — Use web search and codebase exploration before deciding.
Prompting technique: Phase-separation instruction. The skill explicitly distinguishes "evaluation phase (conversation)" from "proposal phase (document writing)" — preventing the agent from conflating exploration with artifact production.
Excerpt 2 — implement-with-tdd Skill (Iron Law)
---
name: implement-with-tdd
description: >
Enforces test-driven development for feature work, bug fixes, and refactoring, activating
for requests such as "implement", "fix", "add feature", "write tests first", or "TDD".
---
# Test-Driven Development (TDD)
## Overview
Write the test first. Watch it fail. Write minimal code to pass.
**Core principle:** Watch the test fail. Only then is it proven to test the right thing.
**Violating the letter of the rules is violating the spirit of the rules.**
## The Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Write code before the test? Delete it. Start over.
**No exceptions:**
- Don't keep it as "reference"
- Don't "adapt" it while writing tests
- Don't look at it for inspiration
Delete it. Write the test. Watch it fail.
## Exceptions (skip TDD only for these)
- Throwaway spikes that will never be merged (branch must be deleted before implementation
begins; any code carried forward requires full TDD)
- Generated code (scaffolded, not behavior-bearing)
- Configuration-only changes
Thinking "skip TDD just this once"? Stop. That's rationalization.
Prompting technique: Iron Law with explicit rationalization-blocker. The phrase "Thinking 'skip TDD just this once'? Stop. That's rationalization." is a meta-instruction that preemptively blocks the agent's own self-justification patterns. This is the same technique as superpowers' Iron Laws.
Excerpt 3 — implement-change Sequential Constraint
**implement-and-validate** subagent per task (sequentially, never in parallel)
Prompting technique: Explicit anti-parallelism instruction. The word "never" prevents the agent from attempting to spawn multiple subagents simultaneously, which would create race conditions in file editing.