si-planning

Elicit structured software requirements with MoSCoW prioritization and traceability matrices.

17|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/insightflo/claude-impl-tools --skill si-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: si-planning
Source: https://github.com/insightflo/claude-impl-tools/tree/main/plugin/skills/si-planning
Command: npx skills add https://github.com/insightflo/claude-impl-tools --skill si-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

SI Planning addresses the challenge of capturing, analyzing, and aligning stakeholder requirements for complex projects, ensuring clear traceability and high-quality artifacts.

Core Features & Use Cases

  • End-to-end requirements elicitation, analysis, and documentation with MoSCoW prioritization and change management.
  • Automatic generation of requirements-analysis, functional-spec, screen-spec, and traceability-matrix artifacts from collected data.
  • Dashboard-driven governance for gaps, progress, and handoff readiness, including domain-specific checklists.

Quick Start

Activate the SI Planning workflow and start collecting domain requirements to generate initial artifacts.

Frequently Asked Questions about si-planning

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

FAQPage Schema
How do I create a traceability matrix for software requirements?

Generate a traceability matrix by capturing functional and non-functional requirements, applying MoSCoW prioritization, and mapping stakeholder needs to artifacts. This ensures gap detection and alignment with ISO 29148 standards for review readiness.

What is the best way to document non-functional requirements for ISO 25010 compliance?

Document non-functional requirements by quantifying them against the ISO 25010 quality model, applying domain-specific checklists, and enforcing IEEE 29148 alignment. This ensures artifacts are structured and ready for stakeholder handoff.

Can I use AI-assisted elicitation for requirements gathering in healthcare projects?

Yes, AI-assisted elicitation supports complex domains including healthcare, finance, and public sector. It applies structured capture and domain-specific checklists to ensure requirements are traceable and aligned with industry standards.

How do I generate functional specification and screen spec documents from collected requirements?

Generate functional specifications and screen specs by activating the planning workflow after collecting domain requirements. The system automatically produces requirements-analysis, functional-spec, and traceability-matrix artifacts from the structured data.

How does MoSCoW prioritization work in requirements traceability and gap detection?

MoSCoW prioritization categorizes requirements into Must, Should, Could, and Won't tiers, enabling structured gap detection and dashboard-driven governance. This ensures clear traceability and highlights missing elements before handoff.

When do I need structured requirements traceability for complex software projects?

Structured requirements traceability is needed when capturing, analyzing, and aligning stakeholder requirements for complex projects across regulated domains. It eliminates ambiguity and ensures artifacts strictly adhere to ISO 29148 and IEEE 29148 standards.