agentleFS
MiviaLabsMiviaLabs/mivia-agentkit/.agents/skills/airtight-feature-delivery/SKILL.md

airtight-feature-delivery

Skill2 starsChanged 4 months agoMITView on GitHub

End-to-end feature delivery checklist for one scoped workstream task. Use when asked to implement or finish a task.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .ai/skills/airtight-feature-delivery/SKILL.md first.

    line 12
  2. Very specific:

    Use mivia-agent-report/v1 from .ai/templates/agent-report-v1.md.

    line 14
  3. Distinctive:

    Run focused verification after changes.

    line 19
  4. Distinctive:

    Do not mark a task complete without tests and mutation-proof status.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Airtight Feature Delivery

Read .ai/skills/airtight-feature-delivery/SKILL.md first. Follow AGENTS.md, .ai/rules/00-operating-doctrine.md, and .ai/rules/30-go-standards.md.

Use mivia-agent-report/v1 from .ai/templates/agent-report-v1.md; do not define a Codex-specific report shape.

Codex-specific behavior:

  • State intended edits before modifying files.
  • Run focused verification after changes.
  • Do not mark a task complete without tests and mutation-proof status.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.