Reusable Markdown AI Prompt: Structure-Preserving Audit

Please provide a comprehensive summary by strictly following the instructions and rules defined below.
Do not deviate from the structure or skip any sub-sections.

# Role
You are a 'Technical HTML Auditor'. Your task is to extract only the official HTML heading elements and provide a 1:1 structural summary.

# Task
Summarize the provided URL while strictly adhering to the original 'Heading Tag' hierarchy.

# Strict Rules (Anti-Hallucination)
1. **Source Code Validation:** You must ONLY include text that is explicitly wrapped in <h1>, <h2>, <h3>, or <h4> tags. 
2. **Exclude Image/Alt Text:** Do NOT extract text from images, alt-text, or captions (e.g., "Traditional vs Agile" is often an image/alt text on this site—if it is not a formal <h> tag, EXCLUDE it).
3. **No Tag Labels:** Do NOT include the labels "<h1>", "<h2>", etc., in your final output. Use Markdown header levels (#, ##, ###) instead.
4. **1:1 Mirroring:** Do not add, skip, or merge any headings. Every official heading must be represented, and no unofficial headings should be created.
5. **Summary Placement:** Write 1 sentences of summary text directly under each valid heading. Start the sentence directly with the subject of the content, avoiding any introductory phrases.
6. **Strict Tag Matching:** ONLY extract text wrapped in <h1> through <h4>.
7. **Zero Tolerance for Styled Divs:** Many sites use <div> or <span> to look like headers. You must IGNORE these. If it is not a semantic <h> tag in the raw HTML, it does not exist.
8. **Verification Step:** After extraction, perform a "Source-to-Tag" cross-check. If "Agile Development Process" does not exist inside an <h> tag in the code, exclude it.
9. **No Logic Inferences:** Do not summarize concepts that aren't formal headers.
10. **Direct DOM Extraction:** Capture the **Full InnerText** of every `<h1>`, `<h2>`, `<h3>`, and `<h4>` tag.
11. **No Truncation:** Do not use ellipses (...) or shorten heading text. You must extract the **entire string** exactly as it appears between the opening and closing tags.
12. **No Logic-Based Synthesis:** Do not invent "category" headings (e.g., "Benefits of Agile") to organize the response. If a phrase is not wrapped in an explicit `<h>` tag in the raw HTML, it must be excluded.
13. **Visual Ignore Rule:** Ignore any text that "looks" like a header due to CSS (font-size, bolding, or `<div>`/`<span>` containers). If it is not a semantic `<h>` tag, it does not exist.
14. **Character-for-Character Accuracy:** Every heading must be a 1:1 mirror of the source code.
15. **No Tag Labels:** Use Markdown header levels (`#`, `##`, `###`, `####`) to represent the tags. Do not type "H1" or "H2" as text.

# Execution Process
- Step 1: Parse the HTML and identify valid <h1> through <h4> tags.
- Step 2: Filter out any text that is actually an image, a div-styled-as-header, or an alt-attribute.
- Step 3: List the exact heading strings using Markdown (#).
- Step 4: Provide the summary under each.

# Target URL
https://i3solutions.com/agile-development/what-is-agile-development-for-software-development/

# Output Language
English

Please provide a comprehensive summary by strictly following the instructions and rules defined below.
Do not deviate from the structure or skip any sub-sections.

# Role
You are a 'Technical HTML Auditor'. Your task is to extract only the official HTML heading elements and provide a 1:1 structural summary.

# Task
Summarize the provided URL while strictly adhering to the original 'Heading Tag' hierarchy.

# Strict Rules (Anti-Hallucination)
1. **Source Code Validation:** You must ONLY include text that is explicitly wrapped in <h1>, <h2>, <h3>, or <h4> tags. 
2. **Exclude Image/Alt Text:** Do NOT extract text from images, alt-text, or captions (e.g., "Traditional vs Agile" is often an image/alt text on this site—if it is not a formal <h> tag, EXCLUDE it).
3. **No Tag Labels:** Do NOT include the labels "<h1>", "<h2>", etc., in your final output. Use Markdown header levels (#, ##, ###) instead.
4. **1:1 Mirroring:** Do not add, skip, or merge any headings. Every official heading must be represented, and no unofficial headings should be created.
5. **Summary Placement:** Write 1 sentences of summary text directly under each valid heading. Start the sentence directly with the subject of the content, avoiding any introductory phrases.
6. **Strict Tag Matching:** ONLY extract text wrapped in <h1> through <h4>.
7. **Zero Tolerance for Styled Divs:** Many sites use <div> or <span> to look like headers. You must IGNORE these. If it is not a semantic <h> tag in the raw HTML, it does not exist.
8. **Verification Step:** After extraction, perform a "Source-to-Tag" cross-check. If "Agile Development Process" does not exist inside an <h> tag in the code, exclude it.
9. **No Logic Inferences:** Do not summarize concepts that aren't formal headers.
10. **Direct DOM Extraction:** Capture the **Full InnerText** of every `<h1>`, `<h2>`, `<h3>`, and `<h4>` tag.
11. **No Truncation:** Do not use ellipses (...) or shorten heading text. You must extract the **entire string** exactly as it appears between the opening and closing tags.
12. **No Logic-Based Synthesis:** Do not invent "category" headings (e.g., "Benefits of Agile") to organize the response. If a phrase is not wrapped in an explicit `<h>` tag in the raw HTML, it must be excluded.
13. **Visual Ignore Rule:** Ignore any text that "looks" like a header due to CSS (font-size, bolding, or `<div>`/`<span>` containers). If it is not a semantic `<h>` tag, it does not exist.
14. **Character-for-Character Accuracy:** Every heading must be a 1:1 mirror of the source code.
15. **No Tag Labels:** Use Markdown header levels (`#`, `##`, `###`, `####`) to represent the tags. Do not type "H1" or "H2" as text.

# Execution Process
- Step 1: Parse the HTML and identify valid <h1> through <h4> tags.
- Step 2: Filter out any text that is actually an image, a div-styled-as-header, or an alt-attribute.
- Step 3: List the exact heading strings using Markdown (#).
- Step 4: Provide the summary under each.

# Target URL
https://i3solutions.com/agile-development/what-is-agile-development-for-software-development/

# Output Language
English