agentleFS
alexderzalexderz/agentic-toolbox/skills/sdlc-artifacts/SKILL.md

sdlc-artifacts

Skill5 starsChanged 46 days agoMITView on GitHub

use this when writing or updating an HLD, LLD, ticket, epic, groom plan, track/roadmap, PoC note, decision, changelog, PR, monthly note, human how-to, or AGENTS stub that the SDLC calls for — copy the matching template and fill required fields. do not use to invent a second process or to skip a gate.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

SDLC artifacts

Fill-in shapes for artifacts the SDLC already requires. Process lives in docs/SDLC.md. Copy a template; do not paste the SDLC into the artifact. No scripts/.

Iron law

One template per artifact. Fill every required field or write n/a and why. Do not invent a parallel outline.

Map

ArtifactStepTemplateLands in
Brief (chunk)Briefdiscover-the-idea (not here)Chat unless asked to file
Incoming itemBrieftemplates/bug.md / task.mdSame files as Groom; fill Proposed fix / Removal / Pick at Brief, not later
Track / roadmapPlantemplates/track.mdBoard project; git copy optional
Chunk / epicBrief–Groomtemplates/chunk.mdBoard parent issue
Groom planGroomtemplates/groom.md.agents/design/<chunk>/groom.md (this skills home: maintainers/design/<chunk>/groom.md); frozen after filing
HLDPlantemplates/hld.mddocs/hld.md or docs/<slug>/hld.md
ComparablesPlantemplates/comparables.mddocs/comparables.md or docs/<slug>/comparables.md
UX / journeysPlantemplates/ux.mddocs/ux.md or docs/<slug>/ux.md
User storyPlantemplates/user-story.mddocs/stories/ or the board
PoCTrialtemplates/poc.mdpoc/poc.md beside the chunk's design records: Trial
LLDSpectemplates/lld.mddocs/lld.md or docs/<slug>/lld.md
MockupsSpectemplates/mockup.mddocs/mockups/ (or n/a)
Decisionanytemplates/decision.mddocs/decisions/<slug>.md
TaskGroomtemplates/task.mdBoard issue, label Task
BugGroomtemplates/bug.mdBoard issue, label Bug
ChangelogBuild / Changelogtemplates/changelog.mdrepo-root CHANGELOG.md
PR / landReviewtemplates/pr.mdPR body or land commit message
MonthlyMonthlytemplates/monthly.mddocs/monthly/, or a Task once filed
Human docSpec+templates/human-doc.mddocs/ how-to (Google style)
Ask the operatorany gatetemplates/ask-human.mdThe message to the operator — not a git file
AGENTS stubRepotemplates/agents-stub.mdproduct-repo AGENTS.md
Repo tracker skillBrief (onboarding)templates/tracker-skill.mdproduct-repo .agents/tracker/SKILL.md

Always

  • Copy the file. Delete unused optional sections. Keep required ones.
  • Link the layer above and below (track → chunk → item; HLD → LLD → ticket). A changelog line cites the ticket ID and the land SHA.
  • Tracker: only the manager writes it: Tracker. The manager files a ticket body with tracker-sdlc create, posts later fields or a design's git path with comment (no edit verb), and sets blockers with set-blocker, not only as text.
  • Dates ISO-8601. Slugs lowercase hyphen.

Ask first

  • A new artifact type that is not in the map.
  • Skipping a required field other than with n/a + why.

Never

  • A second HLD/LLD/ticket outline “just this repo.”
  • Cloning the discover-the-idea brief into templates/.
  • Empty acceptance or empty trust-boundary section on an LLD that touches a boundary.
  • Language skills on a templates-only turn.

Red flags

  • “I’ll freehand the HLD”
  • “Acceptance is ‘it works’”
  • “No blockers, we’ll sequence in chat”

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.