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.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- argos-data-importSkill
- argos-releaseSkill
- awwwards-animationsSkill
- baseline-uiSkill
- bun-file-ioSkill
- design-taste-frontendSkill
- fork-syncSkill
- pi-updateSkill
- react-doctorSkill
- shadcnSkill
- tanstack-formSkill
- tanstack-pacerSkill
- tanstack-querySkill
- tanstack-rangerSkill
- tanstack-routerSkill
- tanstack-storeSkill
- tanstack-tableSkill
- tanstack-virtualSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- vgpuSkill
- viteSkill
- web-design-guidelinesSkill
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
- Very specific: line 10
Use this skill before changing Argos source code, configuration, tests, docs, build scripts, release workflows, or project structure.
- Distinctive: line 14
Create one kebab-case folder per goal:
- Very specific: line 20
If one request contains multiple independent goals, split them into separate folders.
- Distinctive: line 24
Every active goal folder must contain:
- Very specific: line 36
Create or update spec.md, plan.md, and tasks.md.
- Very specific: line 37
Keep the implementation aligned with existing Argos patterns:
- Very specific: line 43
Update tasks.md as work lands.
- Very specific: line 44
Run pnpm run format and pnpm run lint before handoff.
- Distinctive: line 50
Add an archive note when a document references historical code paths.
- Distinctive: line 51
Delete documents that only describe removed code and have no reusable decision record.
- Very specific: line 52
Update docs/README.md when a moved document remains part of the navigation surface.
≈ “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.
Files
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 questionsplan.md: implementation approach, affected interfaces, data flow, compatibility, test strategytasks.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
- Inspect the current code and docs first.
- Pick the target folder from the classification rules.
- Create or update
spec.md,plan.md, andtasks.md. - 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
- Implement the change after the SDD artifacts are complete.
- Update
tasks.mdas work lands. - Run
pnpm run formatandpnpm run lintbefore handoff. Addpnpm run typecheckwhen 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.mdwhen a moved document remains part of the navigation surface.
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
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.

