Create consulting-style proposal slide workspaces and slide plans from user-provided RfP/RFP documents. Use when Codex needs to set up a proposal-slide project folder, create or update DESIGN.md, TASK.md, reuse or create AGENT.md, or derive one-slide-per-task proposal structures from an RfP for Korean public-sector, consulting, or bid-response decks.
Use this skill to turn an RfP into a reusable slide-production workspace, a confirmed design/task baseline, and a proposal-ready slide set.
Prefer Stitch-based slide generation when it is available in the user's environment.
DESIGN.md and TASK.md.DESIGN.md and TASK.md.AGENT.md when it exists. Generate AGENT.md only when it is missing or the user explicitly asks for regeneration.Use this execution priority for slide creation:
DESIGN.md and TASK.md, with html as the required fallback output.Run the initializer when the user wants the project folder structure created automatically.
./scripts/init_project.ps1 -ProjectName <project-folder-name> -BasePath <parent-folder>
Or point directly at the full project path:
./scripts/init_project.ps1 -ProjectRoot <target-folder>
The script creates folders only and writes reminder files that tell the user where to place the RfP and references.
The script creates these folders:
01.Input_RfP02.Reference_Templete03.Reference_Contents_Main04.Reference_Contents_Assistance05.Output_SlideUse -Force to overwrite existing reminder files that were previously scaffolded.
Do not create DESIGN.md, do not create TASK.md, and do not draft slides until the user has placed the actual RfP and relevant references into the workspace.
If the workspace has been scaffolded but the required inputs are missing:
01.Input_RfP.02.Reference_Templete when available.Use the reference files selectively instead of loading everything by default.
references/workflow.md to understand the end-to-end operating model and folder responsibilities.references/design-template.md as the mandatory fallback baseline when 02.Reference_Templete has no usable design reference.references/task-template.md when deriving TASK.md from a user-provided RfP.references/agent-template.md only when the workspace does not already contain a user-provided AGENT.md or the user explicitly asks to regenerate it.Treat a user-provided AGENT.md as authoritative by default.
When the workspace already contains AGENT.md:
DESIGN.md or TASK.md changed.AGENT.md.When building DESIGN.md, the design-source boundary is strict:
02.Reference_Templete is the only workspace folder that may be inspected for visual, formatting, or layout references.03.Reference_Contents_Main and 04.Reference_Contents_Assistance may inform slide content, evidence, or wording, but must not be used as design-reference fallback sources.02.Reference_Templete is empty or unusable, immediately use references/design-template.md.When the user asks for baseline design generation:
01.Input_RfP contains the actual RfP.02.Reference_Templete.03.Reference_Contents_Main, 04.Reference_Contents_Assistance, sibling folders, parent folders, or unrelated files for design-reference fallback.02.Reference_Templete contains template references, reconstruct DESIGN.md from those files while preserving the fixed baseline constraints:
02.Reference_Templete is empty or unusable, use the default baseline from references/design-template.md immediately.Treat TASK.md as a project-specific output, not a fixed asset.
When building TASK.md:
If the RfP is ambiguous, keep the structure generic rather than inventing unsupported detail.
After generating DESIGN.md and TASK.md:
AGENT.md reuse or generation and slide creation.Treat the design baseline from references/design-template.md as mandatory by default:
Default to this sequence unless the user asks for a different workflow:
AGENT.md when the user has provided one. Generate or update AGENT.md only when it is missing or the user explicitly asks for a new project-specific version.05.Output_Slide.When the user asks to create slides, the default output must be an actual slide artifact, not a Markdown stand-in.
05.Output_Slide for working slide artifacts and final outputs.html slide artifacts only.md files as substitutes for slides unless the user explicitly asks for a slide brief, slide script, or Markdown planning documentDESIGN.md, TASK.md, and AGENT.md remain control documents only; they are not slide deliverablesWhen Stitch is unavailable and the user still wants a sample slide quickly, use the bundled script:
python .\proposal-slideformat-generator\scripts\generate_calibration_slide.py --output-dir .\05.Output_Slide --format html
Behavior:
.html slide artifact in 05.Output_SlideDESIGN.mdBefore finalizing any slide plan or deck:
TASK.md.DESIGN.md is internally consistent.Keep SKILL.md lean. Put project-specific detail into the workspace documents and keep reusable logic in references/ and scripts/.