القائمة
Analyses a draft for logical sequence, narrative coherence, and transitions, then reports exactly where the structure breaks down and why.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generates the complete set of metadata fields — tags, categories, keywords, slug, and summary — needed to publish a piece of content in a content management system, ready to copy and paste into each field.
Takes a finished piece of content and produces a complete, archive-ready metadata record — including descriptive tags, subject classifications, rights notes, and an archival summary — for entry into a content management or digital archive system.
Drafts a GDPR compliance note for a specific piece of journalistic content or data collection activity — documenting the lawful basis for processing personal data, what data is held, how long it is retained, and who has access.
Reviews the details of a specific image and flags potential rights clearance issues before publication, identifying which permissions you likely need and which questions to bring to your legal or picture desk.
Reviews a story brief, draft article, or broadcast script and flags potential legal risks — including defamation, privacy, contempt of court, and data protection — so you know what to check before publication.
Drafts a formal, professional request letter to a music rights holder asking for permission to use a track in a specific media production under defined terms.
| name | structure-flow-checker |
| description | Analyses a draft for logical sequence, narrative coherence, and transitions, then reports exactly where the structure breaks down and why. |
| status | stable |
| category | editing |
| subcategory | editing |
| version | 1 |
| eval_score | 4.2 |
| tags | ["structure","narrative-flow","editing","logic","organisation"] |
Analyses a draft for logical sequence, narrative coherence, and transitions, then reports exactly where the structure breaks down and why.
Required: The full draft text — article, script, commentary, or report.
Optional: The intended format (print feature, broadcast package, online explainer), the intended audience (general public, specialist, regional), and the structural logic you were aiming for (e.g. "inverted pyramid," "problem–solution–outcome," "chronological," "scene-setting then argument").
A structured diagnostic report in two parts:
Part 1 — Overall structure assessment (one paragraph) A plain-language summary of how the draft is organised, whether the overall logic holds, and the single most significant structural weakness.
Part 2 — Flagged issues (list) Each issue presented as:
Issues are listed in order of appearance in the draft, not by severity. This makes it easier to work through corrections in sequence.
Length: typically 400–700 words for a 1,000-word draft. Scales proportionally. Tone is direct and collegial — the kind of notes a trusted editor would give.
Format: Print feature article, general interest magazine Intended structure: Profile of a person's career arc — chronological, with a thematic argument running through it Draft:
When Carla Reyes walks onto a building site now, the workers stop what they are doing. Not because she is the project director. Because she is the only woman in sight, and they still aren't used to it.
Reyes grew up in a small coastal town with no engineering tradition. Her father ran a fishing supply business; her mother taught primary school. She won a scholarship to study civil engineering at twenty-two and graduated near the top of her class.
The construction industry has been slow to change. Studies consistently show that women make up fewer than fifteen percent of the engineering workforce globally, and that the figure has barely shifted in a decade. Retention is a bigger problem than recruitment — many women who enter the field leave within five years.
She got her first job at a regional infrastructure firm, working on a bridge reconstruction project. She describes the first months as "learning to exist in rooms where no one expected you." She was promoted to lead engineer within three years, faster than anyone at her level in the firm's recent history.
She now runs a mid-sized construction company she co-founded eight years ago. The firm specialises in public-sector infrastructure — schools, hospitals, water treatment facilities. Last year it completed twelve projects across four regions.
The moment that changed everything came in her third year at the regional firm. A senior colleague dismissed her calculation in a site meeting in front of the full team. She rechecked it that evening. She had been right. She decided then that she would not wait to be given authority — she would build it herself.
Her company now employs forty engineers, a third of them women. She runs a paid internship programme that explicitly targets candidates from underrepresented backgrounds.
Why does any of this matter beyond one person's story? Because the infrastructure built in the next thirty years will shape where people live, how they move, and whether cities can survive climate pressure. The people who design it will determine what gets prioritised. Reyes argues that a homogeneous profession will produce homogeneous answers to problems that are anything but.
Structure Flow Check — Print Feature Profile
Overall assessment
The draft has the right instinct — open with a striking scene, build a biographical arc, layer in the industry context, close with the wider stakes. The biographical thread is clear and the closing argument is strong. The main structural problem is sequencing: the most dramatically significant moment in the subject's life — the site meeting that changed her direction — arrives in paragraph six, buried after two paragraphs of industry statistics and a description of her current company. The reader has already been told where she ends up before they understand the moment that drove her there. This deflates the career arc and weakens the payoff of the closing argument.
Flagged issues
Location: "The construction industry has been slow to change…" (paragraph 3) Problem: This block of industry statistics arrives immediately after the subject's education, before the reader has followed her into the workplace at all. Effect on reader: The reader's momentum into the biographical story stalls. The statistics feel like a detour rather than context, because there is no specific moment in her story yet to attach them to. Suggested fix: Hold this statistics block until after the site meeting scene. It will read as explanation rather than interruption once the reader has seen what she faced personally.
Location: "She now runs a mid-sized construction company…" (paragraph 5) Problem: The current state of her career is described before the pivotal moment that led to it (paragraph 6). Effect on reader: The career arc's dramatic logic collapses. The reader is told the outcome before the cause. When the site meeting scene arrives, it feels like backstory rather than turning point. Suggested fix: Move the description of her current company and its work to after the site meeting scene. The sequence should be: early career → the moment → what she built because of it.
Location: "Her company now employs forty engineers…" (paragraph 7) Problem: This paragraph repeats information already given in paragraph 5 (description of the company) without adding a new dimension. Effect on reader: Slight feeling of having read this before. The two company-description paragraphs should be one, placed after the turning-point scene. Suggested fix: Merge paragraphs 5 and 7 into a single post-turning-point section describing the company she built and the deliberate choices she made in building it.
No issues found in: opening scene (strong), biographical origins (well placed), turning-point scene itself (vivid and specific), closing argument (earns its weight).
