What problem does it solve? Raw requirements and verbal descriptions are messy and incomplete, making it risky to jump straight into an SRS. This Skill turns scattered input into a structured 13-section project background document, marking unknowns as pending and inferences as design assumptions until the user confirms them. ## Core Features & Use Cases - 13-Section Standard Structure: Covers project info, current state, motivation, goals, target visitors, content scope, technical background, boundaries, constraints, success criteria, design assumptions, and pending items. - Iterative Elicitation Loop: Outputs a pending-items list, folds user answers back into the document round by round, and finishes with a confirmed-items summary table that feeds directly into SRS authoring. - No-Fabrication Discipline: Never invents personal information or project names, labels motivational descriptions as unconfirmed facts, and requires draft approval before writing any file. - Use Case: A user says "梳理项目背景" for a GitHub Pages personal site; the Skill produces a full draft with static-site decision points (content source in repo vs local-only, contact form trade-offs, GitHub API rate limits) flagged for confirmation. ## Quick Start Ask the agent to organize your raw requirements into a project background document as input for a later SRS, then answer its pending-items questions round by round.
