collect

Inventory project artefacts from internal and external sources into a unified snapshot.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill collect-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/collect
Command: npx skills add https://github.com/tjisousa/gensem --skill collect-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inventory artefacts from internal projects and external sources, providing a unified view for planning and governance of software projects.

Core Features & Use Cases

  • Internal inventory of current project artefacts and sprint docs
  • External source analysis from local paths or GitHub URLs
  • Centralized .gse inventory with provenance tracking and context-aware recommendations

Quick Start

Invoke /gse:collect with no arguments to inventory the current project artefacts.

Frequently Asked Questions about collect

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

FAQPage Schema
How do I inventory artefacts across internal projects and external sources?

You inventory artefacts by reading .gse configuration files to scan internal projects or external paths and URLs. This process generates a centralized inventory with provenance tracking and context-aware recommendations.

What configuration files are required for project artefact scanning?

Project artefact scanning requires reading .gse/status.yaml, .gse/config.yaml, .gse/sources.yaml, .gse/backlog.yaml, and .gse/profile.yaml. These files apply context-aware rules and adaptive communication during the inventory process.

Can I collect artefacts from external GitHub URLs and local paths?

Yes, you can collect artefacts from external GitHub URLs and local paths using external mode. Internal mode scans the current project, while external mode supports structured multi-step workflows for external source analysis.

What is the best way to create a unified project snapshot for software governance?

The best way to create a unified project snapshot is inventorying artefacts from internal projects and external sources. This provides a centralized .gse inventory with provenance tracking and context-aware recommendations for software governance.

Do I need to configure sprint docs before inventorying project artefacts?

No, you do not need to configure sprint docs before inventorying project artefacts. Invoking the collection process with no arguments automatically inventories current project artefacts and available sprint docs.