kiwi-srs-research

Research requirements and evidence using a 5-subagent topology.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-srs-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiwi-srs-research
Source: https://github.com/Snoworca/speckiwi/tree/main/.agents/skills/kiwi-srs-research
Command: npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-srs-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, external_sources, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting comprehensive research on requirements and evidence, enabling efficient analysis and decision-making.

Core Features & Use Cases

  • Research Execution: Perform detailed research on requirements using a 5-subagent topology.
  • Code Archaeology: Analyze code modules for implementation status, dependencies, and test coverage.
  • External Knowledge: Consult external sources for best practices, standards, and library recommendations.
  • Risk Assessment: Evaluate potential failure modes, anti-patterns, and alternative designs.
  • Use Case: When you need to assess the feasibility of a new feature or evaluate the risks associated with a proposed change, use this Skill to gather comprehensive information.

Quick Start

Use the kiwi-srs-research skill to research the feasibility of implementing a new feature 'feature-x'.

Frequently Asked Questions about kiwi-srs-research

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

FAQPage Schema
How do I assess the feasibility of implementing a new feature in an existing codebase?

To assess feature feasibility, conduct code archaeology to analyze implementation status and dependencies, consult external knowledge bases for best practices, and evaluate potential failure modes using a multi-agent research topology.

What is code archaeology and when do I need it for risk analysis?

Code archaeology examines existing code modules to determine implementation status, dependencies, and test coverage. It is needed during risk analysis to evaluate evidence and identify anti-patterns before proposing changes.

Do I need git and python to research requirements and evidence?

Yes, git and python are required dependencies to execute requirement research. Git provides repository access for code archaeology, while python enables the scripts necessary for the synthesis engine and subagent topology.

How do I evaluate potential failure modes and anti-patterns before a proposed change?

Evaluate failure modes and anti-patterns by utilizing a risk assessment subagent that analyzes code modules against external knowledge bases, identifies alternative designs, and synthesizes findings into a comprehensive evidence report.

What's the best way to consult external sources for library recommendations during requirement research?

The best way to consult external sources is using an external knowledge subagent that queries external knowledge bases for standards and library recommendations, ensuring data integrity and input isolation during the research process.

Does requirement research handle input isolation and data confidentiality?

Yes, requirement research handles input isolation and ensures data confidentiality by design. The synthesis engine and subagent topology process evidence while maintaining strict separation between input data and external knowledge sources.