sdlc-auto-steering

Refreshes private SDLC run steering state from accepted prompt revisions and evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? During an active Agentic SDLC run, accepted prompt revisions, spec changes, and new evidence accumulate without a consistent way to classify them or carry compact reminders into the next phase. This Skill refreshes the private STEERING.md ledger and machine-readable steering state so the coordinator can route the next phase with current context. ## Core Features & Use Cases - Steering Inbox Management: Appends each accepted prompt revision exactly once with a compact redacted summary, never storing raw prompt text, secrets, or customer data. - Disposition Classification: Classifies every unresolved entry as runtime-only, requirements-change, design-change, docs-update, resolved, superseded, rejected, or needs-human. - Routing Signals: Returns routing requests to sdlc-start (for example REPLAN_REQUIRED or HUMAN_INPUT_REQUIRED) instead of choosing the next phase directly. - Use Case: A user edits the managed prompt mid-run; the coordinator invokes this Skill to record the revision, classify its impact, and derive compact reminders before entering the implementation phase. ## Quick Start Ask the Agentic SDLC coordinator to refresh the active run's steering state from the latest accepted prompt revision before selecting the next phase.

Frequently Asked Questions about sdlc-auto-steering

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

FAQPage Schema
How do I update SDLC steering state after a prompt revision?

Invoke the skill through the Agentic SDLC coordinator after sdlc-start accepts a changed prompt revision. It appends the revision to the steering inbox once, classifies it, and refreshes STEERING.md and steering/auto-steering.json with compact reminders.

What is the difference between STEERING.md and auto-steering.json?

STEERING.md is the human-readable private steering ledger, while steering/auto-steering.json holds the same pending disposition state in machine-readable form. Both are updated together and must agree before the skill completes.

Can sdlc-auto-steering edit requirements or design documents?

No. It never edits docs/requirements.md or docs/design.md. Requirements or design changes are classified as routing requests and returned to sdlc-start, which routes them to the owning authoring skills.

Can I run sdlc-auto-steering standalone or as a cron job?

No. It requires verified workflow context from the active Agentic SDLC coordinator and returns without mutation without that evidence. It must not be used as a cron job, daemon, hook orchestrator, or standalone CLI.

How does the skill handle secrets or sensitive prompt content?

It stores only compact redacted summaries of accepted prompt revisions and never persists raw prompt text, secrets, credentials, private endpoints, customer data, or raw logs. Unsafe content is redacted and classified with a safe summary.

What happens when steering entries conflict or run state is missing?

Missing active run state maps to HUMAN_INPUT_REQUIRED and routes to sdlc-start. Conflicting steering that cannot be resolved from product-truth documents is classified as needs-human rather than being forced into a disposition.