agentleFS
XORwellXORwell/archeflow/skills/templates/SKILL.md

templates

Skill0 starsChanged 52 days agoMITView on GitHub

ArcheFlow template gallery: save, share and initialise workflows, team presets, archetypes, domains and bundles.

25 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Check requires files exist

    line 56

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “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

Template Gallery -- Shareable ArcheFlow Configurations

Makes ArcheFlow setups portable and reusable across projects.

Template Storage

LocationScopePrecedence
.archeflow/templates/Project-localHigher (checked first)
~/.archeflow/templates/Global (user-wide)Lower (fallback)

Subdirectories: workflows/, teams/, archetypes/, domains/, bundles/.

Bundles

A bundle is a complete setup (team + workflow + archetypes + domain) in one directory. /archeflow:run reads .archeflow/config.yaml (budget, models, git, test_command, workflow: = fast|standard|thorough) and custom roles; the team and workflow files are documentation of the setup and are not read by the run.

Manifest (manifest.yaml):

name: my-backend-setup
description: "Backend feature work with a security lens"
domain: code
includes:
  team: story-development.yaml
  workflow: custom-workflow.yaml
  archetypes: [custom-archetype.md]
  domain: writing.yaml
requires: []
variables:
  max_cycles: 2
FieldRequiredDescription
nameYesBundle identifier for archeflow-init.sh <name>
descriptionYesHuman-readable description
includesYesFile types to filenames within bundle
requiresNoFiles that must exist in target project
variablesNoKey-value defaults, overridable at init

Operations

<archeflow-root>/lib/archeflow-init.sh <bundle-name> (what /archeflow:init runs)

  1. Find bundle (project-local, then global)
  2. Check requires files exist
  3. Warn before overwriting existing .archeflow/ config
  4. Copy files to .archeflow/ (teams/, workflows/, archetypes/, domains/)
  5. Generate .archeflow/config.yaml with variables

<archeflow-root>/lib/archeflow-init.sh --from <project-path>

  • Copy teams/, workflows/, archetypes/, domains/, config.yaml, hooks.yaml
  • Skip run-specific data: events/, artifacts/, context/, templates/

<archeflow-root>/lib/archeflow-init.sh --save <name>

  • Package current .archeflow/ into ~/.archeflow/templates/bundles/<name>/
  • Auto-generate manifest.yaml

<archeflow-root>/lib/archeflow-init.sh --list

  • Show all bundles and individual templates (global + project-local)

Variable Substitution

Variables in manifests are stored in .archeflow/config.yaml after init. Substitution happens at run time, not template time.

Override at init: <archeflow-root>/lib/archeflow-init.sh backend-feature --set max_cycles=3

Individual Templates

Single files can be copied directly without a bundle:

  • ~/.archeflow/templates/workflows/<name>.yaml
  • ~/.archeflow/templates/archetypes/<name>.md
  • ~/.archeflow/templates/teams/<name>.yaml

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.