davidgomez-sa82

Sdlc Marketplace — AI skill for Claude Code

AI community

A Claude Code plugin marketplace for AI-assisted SDLC work in regulated estates, in any technology it has artifacts for.

How to install Sdlc Marketplace

This entry records only its repository, not the path inside it, so there is no exact command to give. Open davidgomez-sa82/sdlc-marketplace and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sdlc Marketplace does

A Claude Code plugin marketplace for AI-assisted SDLC work in regulated estates, in any technology it has artifacts for. Stack-neutral by construction: the skills carry the procedure, and every language-specific fact lives in a per-technology file.

Alternatives in AI

  • Artifacts Builder — Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web tech 97.5k ★
  • Autoskills — One command. Your entire AI skill stack 6.8k ★
  • Dotai — The ultimate AI development stack, including Claude Code, Task Master, and Curso 1.1k ★

README

sdlc-marketplace

A Claude Code plugin marketplace for AI-assisted SDLC work in regulated estates, in any technology it has artifacts for. Stack-neutral by construction: the skills carry the procedure, and every language-specific fact lives in a per-technology file. Artifacts exist today for .NET/C#, TypeScript/Angular, T-SQL and Python.

One plugin today.

Plugin What
`spec-lifecycle` Constitute, specify, score, implement, test. Five skills plus five deterministic gates. Stack-neutral; artifacts exist for .NET/C#, TypeScript/Angular, T-SQL and Python

Use it

/plugin marketplace add ~/Projects/SA/sdlc-marketplace
/plugin install spec-lifecycle@sdlc-marketplace

The path has to be absolute or start with `./`; a bare `.` is rejected. Once this is on a git remote, the same command takes the repository URL instead of the path.

Check what a plugin costs before adopting it, and after changing it:

claude plugin details spec-lifecycle

How specificity is handled

A skill that says "cite the requirement in a comment using your language's syntax" changes nothing. One that says `// B7:` for C# and `-- B7:` for T-SQL changes a line of code. So the plugins here are specific where it pays and neutral where it does not, split along one seam:

  • The skill carries the procedure and names no language.
  • stacks/.md carries the knowledge for one technology: the trap each forced decision hides behind, the conventions, how to derive a test, and how to read the legacy.
  • gates/profiles/.mjs carries the same facts in executable form, so the gates read the language rather than assuming one.
  • A gate pointed at an unsupported technology refuses and lists what is supported. A silent pass is worse than a refusal, and that was a real defect before this seam existed.

**"Supported" means the artifacts exist.** Four of them: a profile, a prose file, a test template, a