Skip to content
Skills Library
Programming · Research

software

/software

Software engineering research. Use when the user invokes /software or asks for software engineering research — technical landscape and architecture investigations, framework/library/methodology comparison, protocol or standards research, security best-practice verification, reproducibility audits of a codebase or paper-vs-code claims, API and system design prior art. Dispatches to the shared engineering-research method with the software evidence landscape.

Repository
vitruvius ↗
Licence
MIT
Last repository change
17.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Software engineering research. Use when the user invokes /software or asks for software engineering research — technical landscape and architecture investigations, framework/library/methodology comparison, protocol or standards research, security best-practice verification, reproducibility audits of a codebase or paper-vs-code claims, API and system design prior art. Dispatches to the shared engineering-research method with the software evidence landscape.

Arguments

/software <research question> [--deep | --quick]
Original author description

Software engineering research. Use when the user invokes /software or asks for software engineering research — technical landscape and architecture investigations, framework/library/methodology comparison, protocol or standards research, security best-practice verification, reproducibility audits of a codebase or paper-vs-code claims, API and system design prior art. Dispatches to the shared engineering-research method with the software evidence landscape.

How it works

  1. Evidence landscape
  2. Verification criteria
  3. Deliverable shape
  4. Invocation Flags
  5. Gap Detection
  6. Scope and Boundaries
Original SKILL.md headings · 62 lines, 407 words
SKILL.md preview
---
name: software
description: >
  Software engineering research. Use when the user invokes /software or asks
  for software engineering research — technical landscape and architecture
  investigations, framework/library/methodology comparison, protocol or
  standards research, security best-practice verification, reproducibility
  audits of a codebase or paper-vs-code claims, API and system design prior
  art. Dispatches to the shared engineering-research method with the software
  evidence landscape.
argument-hint: "<research question> [--deep | --quick]"
allowed-tools: Write Edit Bash
license: MIT
metadata:
  version: "0.1.0"

---
<!-- VITRUVIUS-COMPILED-SKILL:BEGIN v1 sha256=e2bbd775b4bd49689f0f2f4b0cf9f683bcae390a9e194eb486a00edf1f9b5e75 -->

# Software Engineering Research

Activate the `/skill:engineering-research` method and run it with this
domain payload. Do not restate the research loop here.

## Evidence landscape

- **Primary sources:** official documentation, language/library/framework
  specs and RFCs, source repositories, issue trackers, release notes, vendor
  docs, published benchmarks with a reproducible methodology.
- **Standards bodies:** IETF RFCs, W3C, ISO/IEC, IEEE, NIST — cite the exact
  document + section when one governs.
- **Prior art:** public codebases (read the actual code before describing
  it), architectural decision records, well-cited engineering blogs,
  peer-reviewed systems literature. For papers and academic prior art, use
  the `/skill:scholarly-research` discovery layers (OpenAlex, Semantic
  Scholar, arXiv).
- **Accept with caveats:** established trade press and secondary summaries.
  Deprioritize undated posts, listicles, and social media without primary
  links.

## Verification criteria

- **Claims about code:** read the code or the official doc before describing
  behavior. A repo exists ≠ a feature exists — verify in the source.
- **Version specificity:** claims must name the version, commit, or release
  they were checked against. Unversioned claims are `inferred`.
- **Benchmarks:** a number must trace to a reproducible methodology — harness,
  hardware, dataset, date. "Verified faster" is not a claim.
- **Security:** any security claim must name the exact CVE, advisory, or
  standard (CWE, OWASP) and the version range it applies to.
- **Paper-vs-code audits:** compare claimed methods, defaults, metrics, and
  data handling against the actual code; call out missing code, mismatches,
  ambiguous defaults, and reproduction risks.

## Deliverable shape

Follow the method's artifact contract. In the final artifact, end with a
**Sources** section of URLs (repo, doc, RFC, advisory), each annotated with
what was checked (e.g. "read §2.3 of the spec" or "verified in commit
abc1234"), and mark every claim `verified`, `inferred`, or `blocked`.

## Invocation Flags

Accept `--deep` and `--quick` flags and pass them through to the
`engineering-research` method. See that skill for flag semantics.

## Gap Detection

If research hits an evidence dead-end — no standard, paper, codebase, or
dataset addresses the question after exhausting the discovery layers — suggest
running `/gap-analysis software <sub-topic>` to formally validate and document
the gap. Do not invoke gap-analysis automatically; offer it as a next step and
wait for the user to confirm.

## Scope and Boundaries

- This skill produces research — it does NOT produce final designs or implementation guidance.
- **Research-only, not for final engineering sign-off.** Licensed engineers must review and approve any design based on this research.

Versions

The database has no other skills named software.

Database snapshot: 13.11.2026 · package version 8c0d4f6c9b84 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90research:prior-art
    Research existing solutions when exploring a new problem space. Use when the user mentions "prior art", "existing solutions", "what libraries exist for", or wants to understand the landscape before building.
  • 100software-architecture
    Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
  • 100software-architecture
    Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
  • 100software-architecture
    Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
  • 100software-architecture
    Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development (.NET/C#).
  • 90software-engineering-library
    Route design and code-risk tasks to engineering references. Use for architecture boundaries, interfaces, domain modeling, refactoring, and legacy tests. Also cover data consistency, resilience, and forbidden patterns. Route prior-art questions to programming-advisor. Route…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.