current-spec

Investigate Service, UseCase, and Model specifications into a structured summary.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/t-hasuike/CLysis --skill current-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: current-spec
Source: https://github.com/t-hasuike/CLysis/tree/main/legacy-investigation/skills/current-spec
Command: npx skills add https://github.com/t-hasuike/CLysis --skill current-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically investigate and organize Service/UseCase/Model specifications into a unified, searchable summary to reduce ambiguity and accelerate alignment.

Core Features & Use Cases

  • Rapid investigative discovery (scout mode) to surface key requirements and constraints.
  • Detailed specification documentation that consolidates targets, symbols, dependencies, and readings for knowledge transfer.
  • Use Case: when a project needs a consolidated spec for onboarding, audits, or handoffs.

Quick Start

Ask me to generate a comprehensive current-spec for a given Service/UseCase/Model by providing its name.

Frequently Asked Questions about current-spec

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

FAQPage Schema
How do I organize service specifications for a project onboarding handoff?

Organize service specifications by running a role-based workflow that investigates targets, dependencies, and cross-repo considerations, outputting a structured, searchable summary for onboarding, audits, or handoffs.

What is the best way to discover and document use case requirements across multiple repositories?

Discover and document use case requirements by applying scout mode to perform context checks, identify target files, and consolidate symbols and dependencies into a unified specification document.

Can I capture domain knowledge and model specifications into a single searchable summary?

Capture domain knowledge and model specifications by performing detailed reading and survival checks, which consolidates file paths and dependencies into a unified, searchable summary to reduce ambiguity.

Does this specification documentation workflow enforce any specific roles or processes?

The specification documentation workflow enforces a role-based process with Leader, Planner, Worker, and Inspector roles to systematically manage domain knowledge checks, dependency investigation, and specification output.

What should I provide to start generating a consolidated service or model specification?

Provide the name of the Service, UseCase, or Model to start generating a comprehensive specification that includes target file identification, symbol overviews, and cross-repo considerations.