project-guide

Generate a structured reference guide for project documentation during legacy-system investigations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Present a reference guide for project documentation tailored to the task. Used at mission start and during impact investigation.

Core Features & Use Cases

  • Provides a structured reference order to quickly access system, knowledge, and domain information.
  • Supports project-wide initiation and ongoing impact analysis by mapping relevant sources.
  • Example: when starting a legacy investigation, generate a consistent guide to align team on required references.

Quick Start

Type /project-guide [task overview] to generate the reference guide for your task.

Frequently Asked Questions about project-guide

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

FAQPage Schema
How do I create a structured reference guide for legacy system investigation?

A structured reference guide for legacy system investigation maps required inputs, reference order, and downstream task guidance. It aligns teams on required knowledge sources and phase flows for consistent execution during impact analysis.

What's the best way to align a team on project documentation at task start?

Aligning a team on project documentation at task start requires a structured reference order to quickly access system, knowledge, and domain information. Generating a consistent guide maps relevant sources and phase flows for all members.

How does impact investigation mapping work for ongoing project analysis?

Impact investigation mapping works by generating a consistent reference guide that connects system, knowledge, and domain information sources. It supports ongoing analysis by mapping relevant references and downstream tasks required for execution.

Can I use a reference guide for project-wide initiation and continuous impact analysis?

Yes, a project reference guide supports both project-wide initiation and continuous impact analysis. It maps relevant knowledge sources and reference order to maintain alignment on required documentation throughout the task lifecycle.

Do I need a task overview to generate project documentation references?

Yes, providing a task overview is required to generate the tailored reference guide. The overview allows the guide to map specific required inputs, reference order, and downstream task guidance relevant to that particular investigation.

When do I need a reference guide for knowledge management during phase transitions?

A knowledge management reference guide is needed during phase transitions to map required inputs and reference order. It ensures consistent execution by aligning teams on the necessary system and domain information for the upcoming phase.