sdlc-update-documents

Updates project-facing documentation from implemented and evaluated Agentic SDLC evidence.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-update-documents-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-update-documents
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/sdlc-update-documents
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill sdlc-update-documents-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? After a feature passes implementation, evaluation, or UAT in an Agentic SDLC workflow, project-facing docs like README, changelog, usage guides, and examples often drift from actual behavior. This skill synchronizes those documents with verified implementation evidence without touching requirements or design specs. ## Core Features & Use Cases - Evidence-backed doc updates: Updates README, changelog, usage docs, examples, and generated docs only when implementation, validation, test, and evaluation evidence exists. - Steering integration: Consumes resolved docs-update steering entries and records their disposition as resolved, blocked, or superseded. - Changelog maintenance: Adds a single [Unreleased] entry when user-facing behavior changes, preserving existing grouping. - Use Case: After a feature passes evaluation, the SDLC coordinator routes to this skill to refresh the README and changelog, record documentation evidence under the private run directory, and hand off to spec alignment or PR creation. ## Quick Start Ask the Agentic SDLC coordinator to run the documentation update phase after feature evaluation so project docs match the implemented behavior.

Frequently Asked Questions about sdlc-update-documents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update project documentation after a feature is implemented?

Run this skill through the Agentic SDLC coordinator after evaluation or UAT completes. It compares implemented behavior and evidence against existing docs, updates only what changed, and records documentation evidence under the active run directory.

What documentation files does this skill update?

It updates project-facing files in scope for the active feature: README, user docs, examples, docs indexes, generated docs, and the [Unreleased] changelog section when user-facing behavior changed. It never edits docs/requirements.md or docs/design.md.

Can I invoke sdlc-update-documents standalone outside the SDLC workflow?

No. The skill requires verified workflow context from the active Agentic SDLC coordinator, including project, run, and phase state. Without that evidence it returns without mutation, and it is hidden from the public command menu in Claude Code.

What happens if implementation or evaluation evidence is missing?

Missing implementation, validation, test, or evaluation evidence routes back to the responsible phase. Docs describing multi-layer behavior without evaluated end-to-end slice evidence route back to sdlc-evaluate, and requirements or design drift routes to the spec authoring skills.

Does rerunning the documentation update create duplicate changelog entries?

No. The skill is idempotent: rerunning with unchanged evidence produces a no-op evidence update, preserves existing changelog grouping, and adds only one [Unreleased] entry per behavior change.