Project Proposal Documents: a Tokeny case study

Inputs

• Input file: project-brief.md.
• Brief facts: a school library-corner reservation system for 120 seats; student reservations, administrator management, reservation cancellation, and daily statistics; total budget CNY 60,000; planned duration 6 weeks; a 3-person team; hardware out of scope; availability target 99.5%; only hashed student IDs are to be stored.
• Explicitly pending in the brief: data retention period and launch date.
• Environment reference: ENVIRONMENT.md; only workspace-local inputs and local Python dependencies were used.

Processing Steps

1. Read and structured the brief, separating confirmed facts, proposed content, and pending decisions.
2. Built a 6-week schedule: 1 week research, 1 week solution design, 3 weeks development, 1 week pilot, and 1 week acceptance. Solution design is treated as development preparation in week 2, so the total remains 6 weeks.
3. Created a proposed budget allocation of CNY 8,000, 9,000, 25,000, 8,000, 5,000, and 5,000.
4. Generated proposal.docx with python-docx and budget.csv with Python's CSV module.
5. Ran content and structure checks using python-docx, ZIP/XML reading, and CSV parsing.

Actual Results

• Generated: proposal.docx and budget.csv.
• Budget line items total CNY 60,000; the CSV total row also equals CNY 60,000.
• The Word proposal contains background, scope, proposed solution, budget allocation, a 6-week milestone plan, risks and mitigations, pending items, and a review conclusion.
• The Word title “图书角预约系统项目提案” appears once in the document XML and is configured as black in the title style.
• The DOCX is readable by python-docx; it contains 43 paragraphs and 3 tables.
• The 6-week schedule matches the brief's phases, and no launch date is invented.
• Pending information remains explicitly pending; no specific retention period, date, or business rule was fabricated.

Checks

• CSV: read as UTF-8 with BOM, parse amounts, sum line items, and assert a total of CNY 60,000.
• DOCX: read paragraphs and tables with python-docx; check required sections, budget total, and pending fields; inspect ZIP/XML for readable word/document.xml, title occurrence count, and black title styling.
• Layout: fixed page margins, fixed table column widths, repeating table headers, and one black main title were configured. Table widths were kept within the document text area.

Limitations

• The skill's DOCX schema validator could not run because the environment lacks the defusedxml dependency.
• LibreOffice/soffice was not available locally, so a PDF conversion and page-by-page visual inspection could not be completed. Layout conclusions are based on generation parameters and structural checks, not a manual page review.
• budget.csv is a CSV file and cannot carry Excel-specific column-width or wrap metadata. Clear headers, complete descriptions, and controlled field lengths were used to reduce truncation risk.
• The budget allocation is a proposal for review, not a confirmed payment plan from the brief. Stage amounts, payment milestones, and contingency rules remain subject to confirmation.