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

architect-implement

Skill3 starsChanged 2 months agoApache-2.0View on GitHub

Implement or resume an existing Architect track by executing its approved plan and updating track status. Use when the user asks to implement, continue, resume, or complete a planned Architect track.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tikalk/adlc-team-skills★ 145same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never archive or delete without exact confirmation.

    line 16
  2. Very specific:

    Read references/implement-track-protocol.md, validate context, and confirm the target track.

    line 24
  3. Distinctive:

    Create and verify the final track-scoped commit unless opted out.

    line 28

≈ “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 Implement

Execute one approved track through implementation, verification, synchronization, finalization, and optional cleanup. Follow references/implement-track-protocol.md as the source of truth.

Hard Boundaries

  • Require valid core context and track artifacts; plan.md defines scope and workflow.md defines lifecycle.
  • Capture the worktree before editing. Never stage or commit unrelated or ambiguous changes, and never use broad staging.
  • Preserve the plan's Task status granularity, phase, Manual/Auto, verification, and documentation approval gates.
  • In Auto Mode, continue until finalization; task size and unfinished phases are not reasons to stop or send a final response.
  • Never archive or delete without exact confirmation.

Authorization

The implementation request authorizes one final track-scoped commit unless the user opts out. Auto Mode also authorizes phase checkpoint commits. Manual checkpoints, ordinary task commits, cleanup commits, and unrelated commits require separate authorization.

Run

  1. Read references/implement-track-protocol.md, validate context, and confirm the target track.
  2. Load track and project context, capture the worktree baseline, and select Manual or Auto Mode.
  3. Execute tasks and phase verification in state order.
  4. Complete track bookkeeping and synchronize approved project documentation.
  5. Create and verify the final track-scoped commit unless opted out.
  6. Offer review, archive, delete, or skip cleanup under the protocol's approval rules.

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