agentleFS
Sign inStart free
Luis85Luis85/agentic-workflow/.github/copilot-instructions.md

agentic-workflow

Copilot instructions0 starsChanged 6 months agoMITView on GitHub

This repository is Specorator — a template for spec-driven, agentic software development. The workflow itself is the deliverable. AGENTS.md is the single source of truth for workflow rules, agent roles, operating conventions, and repo layout. Read it before making changes. Supporting context (in load order): This file is a Copilot-specific thin pointer. It does not replace AGENTS.md. When AGENTS.md Tool-specific notes changes, sync this file accordingly. See docs/adapters.md.

The file

We split this copilot-instructions.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    All implementation derives from specs.

    line 19
  2. Very specific:

    Use imperative commit messages referencing task IDs: feat(area): add T-AREA-NNN description.

    line 20
  3. Very specific:

    Do not commit directly to main or develop.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

GitHub Copilot instructions

This repository is Specorator — a template for spec-driven, agentic software development. The workflow itself is the deliverable.

Source of truth

AGENTS.md is the single source of truth for workflow rules, agent roles, operating conventions, and repo layout. Read it before making changes.

Supporting context (in load order):

  1. AGENTS.md — project conventions, agent classes, operating rules
  2. memory/constitution.md — governing principles
  3. .claude/memory/MEMORY.md — operational memory index
  4. docs/specorator.md — full lifecycle workflow definition
  5. specs/<feature>/workflow-state.md — active feature state

How to work here

  • All implementation derives from specs. Read the relevant specs/<slug>/ before writing code.
  • Use imperative commit messages referencing task IDs: feat(area): add T-AREA-NNN description.
  • One concern per branch. Verify locally before pushing: npm run verify.
  • Do not commit directly to main or develop.

Adapter note

This file is a Copilot-specific thin pointer. It does not replace AGENTS.md. When AGENTS.md Tool-specific notes changes, sync this file accordingly. See docs/adapters.md.

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