sdlc-gather-context

Gathers vendor, codebase, and test evidence into a feature-specific context pack for design planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Design and implementation work often stalls because engineers lack verified technical facts about vendors, internal systems, and existing code. This Skill collects only the evidence needed for one feature and produces a compact, source-traceable context pack before design begins. ## Core Features & Use Cases - Evidence-Based Context Packs: Gathers official vendor docs first, internal docs second, and code/tests third, recording exact versions, APIs, and constraints. - Layer and Boundary Analysis: Captures layer owners, API contracts, data contracts, and integration seams when a feature spans a vertical slice. - Idempotent Updates: Reuses existing context packs when sources are unchanged and marks affected design blocks stale when sources change. - Use Case: Before designing a new FEAT-12 checkout flow, run this Skill to produce context/FEAT-12.context.md with verified vendor API limits, existing service contracts, and open context questions. ## Quick Start Ask the Agentic SDLC coordinator to gather context for FEAT-12 and produce a context pack before design.

Frequently Asked Questions about sdlc-gather-context

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

FAQPage Schema
How do I gather technical context before designing a feature?

Provide one REQ or FEAT identifier and any relevant links, then the Skill collects official vendor facts, internal docs, and code or test evidence into a context pack. The output records design implications, layer contracts, and open blockers with source traceability.

What is a context pack in an agentic SDLC workflow?

A context pack is a compact Markdown file (context/FEAT-*.context.md) containing verified facts, source lists, design implications, layer and boundary evidence, and open questions for one feature. It is created from a template and reused idempotently when sources are unchanged.

Can I invoke sdlc-gather-context directly as a standalone command?

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

What happens when official vendor documentation is unavailable?

The Skill states that the behavior could not be verified rather than guessing. If internal docs conflict with vendor docs, it records the conflict and prefers official docs unless internal platform behavior overrides them.

When should I not use context gathering for a feature?

Do not use it to implement code, make design decisions without evidence, or dump raw webpages, Slack threads, or logs. It also must never store secrets or private tokens in context packs.