メニュー
Impact analysis using sphinx-needs dependency trees. Discovers affected specification elements by traversing traceability links. USE FOR: change scoping, blast radius analysis, element discovery before spec writing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How managers invoke engineers as subagents. 'Invoke' in any syspilot agent doc means runSubagent(). The agents: list in YAML frontmatter declares which agents can be called. Managers orchestrate — engineers execute and return structured results. USE FOR: understanding agent communication, runSubagent() calls, agents: frontmatter semantics.
Git branching strategy and commit conventions for syspilot. Development branch with feature branches, main = releases only. Who may create/commit to which branches. USE FOR: any git operation, branch creation, committing, pushing, merging.
Session-to-Session (S2S) messaging for Copilot CLI agents. Use this skill whenever you need to send a message to another agent session, check your inbox, receive a pending message, or list active sessions. Triggers include: "send to session", "check inbox", "receive message", "message agent", "notify session", "S2S", "session-to-session", or any request to communicate with another named Copilot CLI session.
| name | syspilot.impact-python |
| description | Impact analysis using sphinx-needs dependency trees. Discovers affected specification elements by traversing traceability links. USE FOR: change scoping, blast radius analysis, element discovery before spec writing. |
Implements: SYSP_SPEC_SKILL_IMPACT_QUERY, SYSP_SPEC_SKILL_IMPACT_EXCHANGE Requirements: SYSP_REQ_SKILL_IMPACT_QUERY, SYSP_REQ_SKILL_IMPACT_EXCHANGE
.github/skills/syspilot.impact-python/scripts/get_need_links.py — run with --help for parameter details.
Requires docs/_build/html/needs.json — run sphinx-build first if stale.
To replace this implementation: create a new skill folder, provide the same
query-by-ID capability, update the description for Copilot discovery.
No agent changes required.
Impact Analysis is mandatory for every change. File lists provided in a Change Request are input hints, not the complete scope. This skill MUST be executed before any spec changes are made — the result defines the actual scope.
A newly created element has no incoming links. Run the query from each consumer element that the new element satisfies.
Example: You created SYSP_US_SKILL_IMPACT which :links: to SYSP_US_DESIGN
and SYSP_US_PM. Run the impact query from SYSP_US_DESIGN and SYSP_US_PM
(not from the new US).
--direction in for level transitionsin = "who links to me" = "who implements me at the next level down".
REQs link upward to USes, SPECs link upward to REQs. So querying a US with
--direction in yields its REQ candidates.
| Transition | Depth | Rationale |
|---|---|---|
| Level 0 → Level 1 | 1 | US → REQ, direct links |
| Level 1 → Level 2 | 1 | REQ → SPEC, direct links |
| Level 2 cross-check | 2 | Catches second-order consumers (e.g. doc SPECs aggregating workflow SPECs) |
At Level 0 present candidates to the user without verdicts. Assessment (affected / not affected) happens when writing the next level.