agentleFS
Sign inStart free
peterbamuhigirepeterbamuhigire/chwezi-dev-engine/skills/sdlc-meta/sdlc-documentation/SKILL.md

sdlc-documentation

Skill31 starsChanged 18 days agoMITView on GitHub

Use when producing, reviewing, or consolidating SDLC documentation across planning, requirements, design, testing, deployment, user rollout, post-deployment, and maintenance phases. Load absorbed SDLC phase references as needed.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this parent skill as the active SDLC documentation entrypoint.

    line 14
  2. Distinctive:

    Every document must be tied to a decision, acceptance criterion, release gate, or operating obligation.

    line 48
  3. Distinctive:

    Avoid generic SDLC text that cannot guide an implementation or audit decision.

    line 50
  4. Distinctive:

    Read and search are required.

    line 88

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

SDLC Documentation

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use this parent skill as the active SDLC documentation entrypoint. Keep the phase-specific details in references and load only the phase being authored or reviewed.

<!-- dual-compat-start -->

Use When

  • Creating or reviewing SDLC document sets, delivery evidence, traceability, phase gates, and lifecycle handoffs.
  • Consolidating planning, design, testing, deployment, user rollout, post-deployment, and maintenance documents.
  • Aligning project documentation with implementation, validation, release, and support obligations.

Do Not Use When

  • The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow.
  • The request only needs a trivial answer and no reference module needs to be loaded.

Required Inputs

ArtefactRequired?Purpose
System, repository, environment, and constraintsyesGround the document in actual delivery context
Requested lifecycle phase and audienceyesSelect only the needed reference and output

Workflow

  1. Load world-class-engineering for baseline delivery quality.
  2. Load the needed phase reference:
    • references/sdlc-planning.md for project planning and initiation.
    • references/sdlc-design.md for solution and technical design documents.
    • references/sdlc-testing.md for test planning, evidence, and acceptance gates.
    • references/sdlc-user-deploy.md for user rollout and adoption documents.
    • references/sdlc-post-deployment.md for go-live review and stabilisation evidence.
    • references/sdlc-maintenance.md for support, maintenance, and continuous improvement.
  3. Pair with project-requirements, advanced-testing-strategy, deployment-release-engineering, or implementation-status-auditor when the task needs those outputs.

Quality Standards

  • Every document must be tied to a decision, acceptance criterion, release gate, or operating obligation.
  • Preserve traceability from requirement to design, implementation, test evidence, release, and support.
  • Avoid generic SDLC text that cannot guide an implementation or audit decision.

Anti-Patterns

  • Treating absorbed reference files as active skills or separate routing entrypoints.
  • Loading every migrated child reference instead of the one that matches the task.
  • Producing generic advice without constraints, evidence, or next verification steps.

Outputs

  • SDLC document, review findings, traceability notes, phase gate checklist, or handoff package.

Evidence Produced

CategoryArtifactFormatExample
CorrectnessTraceability resultsMatrixRequirement-to-test mapping
SecuritySecurity reviewFindings registerUnresolved authorization risk
Data safetyData-control evidenceChecklistRecovery verification
PerformancePerformance verificationTest recordSLO result
OperabilityOperational handoffRunbook and checklistMonitoring ownership
UX qualityUser validationAcceptance recordAccessibility result
Release evidenceRelease decisionApproval recordSigned gate outcome

References

  • Load only the references/<old-skill>.md files named in the workflow when their depth is required.
<!-- dual-compat-end -->

Decision Rules

ConditionAction
One lifecycle phase is requestedLoad only its absorbed reference
Evidence conflicts with an older documentFlag and reconcile before update
Required operational fact is unknownMark it open; do not invent it

Capability Contract

Read and search are required. Editing and validation execution require authorisation.

Degraded Mode

Fallback: without repository evidence, return a document skeleton and open-question register.

Domain Anti-Patterns

  • Copying every phase template into one document.
  • Presenting planned behaviour as implemented.
  • Omitting owner or acceptance evidence.
  • Leaving stale cross-document contradictions.
  • Inventing deployment or maintenance facts.

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