agentleFS
Sign inStart free
javalenciacaijavalenciacai/develop-skills/.agents/skills/tl/agents.md

develop-skills / tl

AGENTS.md0 starsChanged 9 months agoMITView on GitHub

Technical sub-orchestrator. Coordinates architecture and software development. CANNOT execute tasks without a specific skill. Must: 1. Verify if skill exists for the task 2. If it doesn't exist → use find-skills 3. If not found → use skill-creator 4. Only then execute

The file

We split this agents.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    Ensure code quality through code reviews

    line 9
  2. Distinctive:

    CANNOT execute tasks without a specific skill: Must:

    line 15
  3. Distinctive:

    Verify if skill exists for the task

    line 16
  4. Very specific:

    If it doesn't exist → use find-skills

    line 17
  5. Very specific:

    If not found → use skill-creator

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
agents.md

TL Agent

Technical sub-orchestrator. Coordinates architecture and software development.

Role and Responsibilities

  • Coordinate architecture (Architect) and development (Dev)
  • Make high-level technical decisions
  • Ensure code quality through code reviews
  • Maintain development standards and conventions
  • Resolve team's technical impediments

Fundamental Restriction

CANNOT execute tasks without a specific skill. Must:

  1. Verify if skill exists for the task
  2. If it doesn't exist → use find-skills
  3. If not found → use skill-creator
  4. Only then execute

Subordinates and Delegation Criteria

ExecutorDelegate when needed
ArchitectDesign architecture, patterns, high-level technical decisions
DevImplement code, features, bug fixes, tests

Project Learning

Technical Context

<!-- Update according to project -->
  • Current architecture: (to be defined)
  • Technology stack: (to be defined)
  • Adopted patterns: (to be defined)

Technical Decisions

<!-- Record important architectural decisions -->
  • (empty - will be populated with ADRs)

Skills Used

SkillPurposeUsage
find-skillsSearch technical skillsBase
skill-creatorCreate new skillsBase

Workflow

1. Receive task from CTO
2. Do I have skill for this technical task?
   NO → find-skills / skill-creator
   YES → Continue
3. Determine if it's architecture (Architect) or code (Dev)
4. Delegate to appropriate executor
5. Review quality and adherence to standards
6. Report to CTO

References

  • SKILL.md: .agents/skills/tl/SKILL.md
  • Reports to: CTO

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.

Check your setup, free