agentleFS
Sign inStart free
hlhr202hlhr202/swe-skills/skills/architect-discuss/SKILL.md

architect-discuss

Skill3 starsChanged 2 months agoApache-2.0View on GitHub

Use only when the user explicitly includes `architect-discuss` or directly asks to use the architect-discuss skill. Turns raw or ambiguous product and technical requirements into a product and architecture draft before tracked Architect proposal work.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not create tracked Architect artifacts, modify implementation code, scaffold systems, or run implementation validation.

    line 13
  2. Distinctive:

    Do not commit unless explicitly requested in the current conversation.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Architect Discuss

Clarify early product and technical direction before tracked proposal work. Follow references/discuss-protocol.md as the source of truth.

Hard Boundaries

  • Require explicit architect-discuss invocation.
  • Do not create tracked Architect artifacts, modify implementation code, scaffold systems, or run implementation validation.
  • Save a standalone draft only to a user-confirmed safe relative path; never overwrite without exact confirmation.
  • Do not commit unless explicitly requested in the current conversation.

Run

  1. Read references/discuss-protocol.md.
  2. Qualify the trigger and build only the repository context needed for the discussion.
  3. Progress through resumable gates; ask only material questions and auto-pass established decisions.
  4. Generate the synthesis only after readiness, or explicitly label unresolved synthesis.
  5. Offer continue, save, split, proposal handoff, or stop. Never execute the handoff automatically.

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