agentleFS
dvaJidvaJi/argos/.agents/skills/argos-sdd/SKILL.md

argos-sdd

Skill4 starsChanged 4 days agoApache-2.0View on GitHub

Use for any Argos code, configuration, documentation, feature, issue fix, refactor, or architecture change before implementation. This skill enforces the project SDD workflow: classify the goal, create or update spec.md, plan.md, and tasks.md under docs/features, docs/issues, or docs/architecture, resolve NEEDS CLARIFICATION items, then implement and validate.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Use this skill before changing Argos source code, configuration, tests, docs, build scripts, release workflows, or project structure.

    line 10
  2. Distinctive:

    Create one kebab-case folder per goal:

    line 14
  3. Very specific:

    If one request contains multiple independent goals, split them into separate folders.

    line 20
  4. Distinctive:

    Every active goal folder must contain:

    line 24
  5. Very specific:

    Create or update spec.md, plan.md, and tasks.md.

    line 36
  6. Very specific:

    Keep the implementation aligned with existing Argos patterns:

    line 37
  7. Very specific:

    Update tasks.md as work lands.

    line 43
  8. Very specific:

    Run pnpm run format and pnpm run lint before handoff.

    line 44
  9. Distinctive:

    Add an archive note when a document references historical code paths.

    line 50
  10. Distinctive:

    Delete documents that only describe removed code and have no reusable decision record.

    line 51
  11. Very specific:

    Update docs/README.md when a moved document remains part of the navigation surface.

    line 52

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

Argos SDD

When To Use

Use this skill before changing Argos source code, configuration, tests, docs, build scripts, release workflows, or project structure.

Classify The Goal

Create one kebab-case folder per goal:

  • New capability, user-visible behavior, integration, or tool: docs/features/<goal>/
  • Bug, regression, failing test, CI failure, reliability problem, or prompt/runtime issue: docs/issues/<goal>/
  • Refactor, migration, dependency boundary, shared contract, runtime architecture, or cross-module design: docs/architecture/<goal>/

If one request contains multiple independent goals, split them into separate folders. Keep current architecture reference docs such as docs/architecture/agent-system.md in place; use subfolders for new architecture targets.

Required Artifacts

Every active goal folder must contain:

  • spec.md: user need, goal, acceptance criteria, constraints, non-goals, open questions
  • plan.md: implementation approach, affected interfaces, data flow, compatibility, test strategy
  • tasks.md: ordered tasks that can map to commits or review slices

Resolve every [NEEDS CLARIFICATION] marker before implementation. If a requested change is tiny, keep the files short and concrete.

Workflow

  1. Inspect the current code and docs first.
  2. Pick the target folder from the classification rules.
  3. Create or update spec.md, plan.md, and tasks.md.
  4. Keep the implementation aligned with existing Argos patterns:
    • main process Presenter boundaries
    • typed shared/contracts/*
    • renderer api/*Client
    • the current renderer's component and state patterns
  5. Implement the change after the SDD artifacts are complete.
  6. Update tasks.md as work lands.
  7. Run pnpm run format and pnpm run lint before handoff. Add pnpm run typecheck when the change touches TypeScript surfaces.

Documentation Hygiene

  • Move completed or stale SDD target folders to docs/archives/<goal>/.
  • Add an archive note when a document references historical code paths.
  • Delete documents that only describe removed code and have no reusable decision record.
  • Update docs/README.md when a moved document remains part of the navigation surface.

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.