메뉴
This skill should be used when an architect needs to understand Taiwan's public review (公開閱覽) procedures for government procurement, including how to review tender documents, provide professional feedback, and evaluate project opportunities before formal bidding.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | public-review |
| description | This skill should be used when an architect needs to understand Taiwan's public review (公開閱覽) procedures for government procurement, including how to review tender documents, provide professional feedback, and evaluate project opportunities before formal bidding. |
| user-invocable | true |
| metadata | {"class":"C"} |
This skill covers Taiwan's public review (公開閱覽) process under the Government Procurement Act, a pre-tender procedure where procurement documents are made available for industry feedback. Invoke this skill when reviewing upcoming procurement opportunities, preparing feedback on tender documents, or evaluating whether to participate in subsequent formal bidding.
| Law | Article | Content |
|---|---|---|
| Government Procurement Act (政府採購法) | Art. 34 | Public review requirements for tender documents |
| Enforcement Rules | Art. 43 | Detailed procedures for public review process |
| Public Construction Technical Service Contract Template | Full text | Standard contract clauses reference |
| Condition | Requirement |
|---|---|
| Above announcement threshold (≧ NTD 1,000,000) | May conduct public review |
| Complex or large-scale projects | Recommended by PCC guidelines |
| Projects with novel technical requirements | Recommended to reduce disputes |
| Above audit threshold (≧ NTD 50,000,000) | Strongly recommended |
1. Publication
└─ Procuring entity posts notice on Government e-Procurement System
└─ Documents made available for download/inspection
2. Review Period
└─ Typically 5-7 working days
└─ Minimum period per PCC guidelines
3. Feedback Submission
└─ Written comments submitted by interested parties
└─ Format: per procuring entity requirements (usually written/email)
4. Agency Response
└─ Procuring entity compiles all feedback
└─ Public response to each comment (accepted/rejected with rationale)
5. Document Revision
└─ Tender documents revised based on accepted feedback
└─ Revision history documented
6. Formal Tender
└─ Revised documents used for formal bidding process
| Area | What to Check | Common Issues |
|---|---|---|
| Scope Definition | Clear work items, deliverables | Ambiguous scope, missing items |
| Fee Calculation | Alignment with official fee standards | Below-standard fees, unclear payment schedule |
| Design Timeline | Reasonable duration per project complexity | Unrealistic deadlines |
| Evaluation Criteria | Weight distribution, objectivity | Over-emphasis on price vs. quality |
| Contract Terms | Risk allocation, liability clauses | Unfair risk transfer to service provider |
| Penalty Clauses | Delay penalties, liquidated damages | Excessive penalty rates |
| Technical Requirements | Specifications clarity | Restrictive specs limiting competition |
| Category | Priority | Example |
|---|---|---|
| Legal compliance | High | Contract clause contradicts Procurement Act |
| Fee adequacy | High | Fee below 機關委託技術服務廠商計費標準 minimum |
| Timeline feasibility | High | Design period insufficient for required regulatory reviews |
| Risk allocation | Medium | Unfair force majeure clause |
| Technical clarity | Medium | Ambiguous performance specifications |
| Competition fairness | Medium | Specs written for specific vendor |
| Practice | Rationale |
|---|---|
| Submit specific, actionable feedback | Generic complaints are less likely to result in changes |
| Reference official standards and regulations | Strengthens the basis for requested changes |
| Coordinate through professional associations (建築師公會) | Collective feedback carries more weight |
| Maintain written records of all submissions | Documentation for potential future disputes |
| Attend pre-bid meetings if offered | Additional context beyond written documents |
# Search Government Procurement Act provisions on public review
taiwan-building-code_search_building_code(query="政府採購法 公開閱覽")
# Search interpretations on tender document requirements
taiwan-building-code_search_building_interpretations(query="招標文件 公開閱覽")
# Download procurement-related specifications
pcc-downloader_download_specification(chapter="procurement", keyword="公開閱覽", format="pdf")
This skill should be used whenever producing a consulting answer or authoring/editing a knowledge-base skill, to control how facts are sourced and how uncertainty is expressed: it defines the source-control iron rule (never infer un-transcribed numeric values from general practice), the three certainty labels (Verified / Secondary / Unverified), the ERROR/WARNING/INFO check-output convention, the To-Verify section format, and the tone rules that prevent confidently-wrong output.
This skill should be used when a contributor wants to submit a new skill, edit an existing skill, or make any change to the Taiwan Architect KB repository. It guides the full lifecycle: clone/fetch, branch, create/edit, self-validate, and submit PR.
This skill should be used when checking stair dimensional compliance for buildings in Taiwan — minimum stair-and-landing width, riser height, tread depth by building-use category, and the critical handrail-encroachment rule (clear width must remain >= 75 cm regardless of handrails), per Taiwan Building Technical Regulations (Design & Construction) Article 33, Chapter 2 Section 7 (Stairs, Railings, Ramps, Articles 33-39). Railings (Art. 38), handrails (Art. 37) and ramps (Art. 39) are stubbed for later completion.
This skill should be used when an architect receives just an address or lot number (地號) for a site in Taichung City, Taiwan, and needs to quickly understand the land's basic data — zoning, registered land area, land value, building numbers and permits, building overlay/footprint status, urban planning land-use regulations, geological hazard zones, slope-land restrictions, fire-break setback zones, active fault distances, and sewer connection announcements — while also getting a head start on the official PDF certificates commonly needed as supporting documents for a later building permit application. Trigger scenarios: evaluating site feasibility right after receiving an address/lot number, checking land-use restrictions and pre-gathering supporting documents before a permit application, due diligence before a real-estate transaction, or converting a Taichung street address to its lot number. Taichung City only — does not work for other Taiwan counties/cities.
This skill should be used when architects or project teams need to query, organize, compare, or source-check Taiwan public works quality-management references, inspection forms, supervision references, traffic-maintenance references, occupational safety references, PCIC construction specifications, and public works checklist sources.
This skill should be used when verifying CNS (Chinese National Standards) on public engineering drawings or querying PCC (Public Construction Commission) guide specifications.