system-help

Answers questions about the SDLC Documentation Generator and logs every Q&A to a knowledge base.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill system-help-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-help
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/utility/system-help
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill system-help-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users of the SDLC Documentation Generator often have questions about how the system works—approvals, signatures, file locations, workflow rules—and answers get lost in chat history. This Skill answers system-level questions and permanently logs every Q&A to a growing knowledge base so answers are reusable. ## Core Features & Use Cases - System Question Answering: Responds to "how do I", "what is", "can I", and "why does" questions about workflows, signatures, sources files, and project structure. - Mandatory Knowledge Base Logging: Appends every question and answer to QA.md with a date stamp, building a living FAQ over time. - Scope Detection: Distinguishes system questions from project-specific requests and routes the latter to skills like /utility/project-status. - Use Case: A new team member asks "how do I approve a document?" The agent answers with the signature approved command and logs the Q&A so the next person finds it instantly in QA.md. ## Quick Start Ask the agent a question about how the system works, such as "what is a signature file and where is it stored?"

Frequently Asked Questions about system-help

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

FAQPage Schema
How do I approve a document in the SDLC Documentation Generator?▼

Say "signature approved" after reviewing the document. The agent updates the signature file with your Git identity, marks the checklist as SIGNED, commits to Git, and proceeds to the next skill.

What is a sources file in the SDLC workflow?▼

A sources file tracks all information used to generate a document: user Q&A history, referenced previous documents, external research, and identified information gaps. It lives at `sources/{phase}-{skill}-sources.md` and enables iterative improvement.

Can I skip a skill in the SDLC phase sequence?▼

Yes. Mark the skill as "N/A" in its signature file with a note explaining why it does not apply, then say "signature approved". The skill is recorded as completed with N/A status and the next skill unlocks.

When should I use system-help instead of project-status?▼

Use system-help for generic questions about how the system works, such as concepts, commands, and file locations. Use `/utility/project-status` for questions about a specific project's progress, pending items, or next actions.

Why can't I proceed to the next skill after generating a document?▼

Each skill requires the previous skill to be signed before advancing. Check `checklist.md` in your project folder for blocking items, then approve or mark pending documents as N/A to unlock the next step.