Software-Copyright-Material-Generation-Skills-for-Codex

Build a structured application draft from confirmed facts and traceable feature evidence. Use when application materials are needed after intake. Do not use for marketing copy, README work, or unrelated writing tasks.

Generate source code evidence materials from approved features and repository evidence. Use when formal source code materials are needed. Do not use before feature boundaries are approved.

Build manual artifacts and maintain the semi-automatic manual manifest workflow. Use when formal manual or design documentation is needed after features are reviewed. Do not use to invent screenshots or UI that do not exist.

Build a reviewed feature map that connects functions to code, manual sections, screenshots, and application claims. Use after repository scanning when formal function boundaries are needed. Do not use for simple provisional drafting without feature review.

Build and validate ownership evidence checklists from the declared development mode. Use when proof documents are needed for formal review. Do not use for unrelated writing or code analysis.

Validate completeness, consistency, traceability, and submission readiness across generated filing materials. Use after artifacts are produced. Do not use for minor copy-editing or non-filing tasks.

Collect and normalize explicit software copyright application facts. Use when a soft copyright workflow starts or project facts are missing. Do not use for generic debugging, code review, or README summarization.

Analyze a repository for candidate stack, entry points, modules, routes, and code evidence files. Use after intake when repository evidence is needed. Do not use to finalize legal facts.