team_profile_revised ยท diff
git:20260905.97621c1 to git:20260906.f9cef19
52 added, 11 removed. Audit A to A.
---
name: team_profile_revised
- description: Assess a startup's active founders using data-room team checklists, then synthesize findings and evidence references by category. Use for the revised checklist workflow alongside team_profile.
+ description: Assess active founders with data-room checklists and synthesize material findings by category. Use for the revised checklist workflow alongside team_profile, with the same checklists for screening and due diligence.
---
- Run the repository pipeline:
+ # Revised team profile
- ```bash
- python -m skills.harness /team_profile_revised "<STARTUP_NAME>"
- ```
+ Synthesize founder-team strengths, concerns and evidence gaps from category audits.
- Or use `python -m skills.team_profile_revised --dataset "<STARTUP_NAME>"`.
+ ## Inputs and outputs
- The pipeline prepares cached `startup_profile` and `person_profile` artifacts for all related persons. Use the existing manual `persons_in_dataset` roster as the authoritative list, including an intentionally empty list. If the roster is absent, stop with a missing-roster error; this workflow never triggers person discovery. The separate `persons_in_dataset` skill can create it. Profile generation uses the standard `person_profile` workflow, including LinkedIn enrichment, dataset evidence and configured founder-trait instructions. The registry and direct team calls use identical settings and reuse the same profiles. The founder-trait section belongs to `person_profile`; other related persons remain factual profiles. Person profiles use the standard identifier order (LinkedIn ID, email address, full name) and `<identifier>-<model>.md` filenames; generation settings are tracked in cache metadata, without filename suffixes.
+ The async `team_profile_revised(startup_name)` returns a one-element
+ `list[InsightFile]` containing the category synthesis. Structured checklist
+ JSON artifacts remain internal. An existing manual person roster is required;
+ an intentionally empty roster is valid.
- The shared startup and person profiles precede question-specific evidence in the cacheable prompt prefix. Four Markdown checklists in `config/team_profile_revised/checklists/` follow the hierarchy, with subcategories as chapters. `batch_audit` searches the data room separately for each check and saves its standard structured JSON artifacts. If search returns no new chunks, shared profile evidence can still support an answer; retrieval errors remain technical failures.
+ ## Workflow and dependencies
- Use the same checklists for screening and due diligence. Focus the assessment on active founders; bring the larger team into findings only where material to execution, support or governance. Keep missing information distinct from actual shortcomings. Do not generate scores or perform additional public checks or outreach beyond the standard profile dependencies.
+ Prepare and synchronize the startup, then request `startup_profile` and
+ `person_profile_as_person_objects(..., names=None)` before checking the final
+ cache. Read people exclusively from the existing roster through the standard
+ [person-profile workflow](../person_profile/SKILL.md), with the same settings
+ as the registry. Never trigger discovery from this workflow.
- The final Markdown insight contains a synthesis per main category, with original Q/N/R IDs, supporting document references and material follow-ups. Technical audit errors stop synthesis; successful audit artifacts remain reusable. Cache keys cover dependency configuration and actual profile content as well as checklists and synthesis instructions.
+ Pass shared profiles before question-specific evidence in the cacheable prompt
+ prefix. Run the four configured category checklists through `batch_audit`;
+ each check searches the dataset. Shared profile evidence can support an answer
+ when retrieval succeeds without new chunks.
- For checklist maintenance, read [checklist decisions and ID mapping](references/checklist_decisions.md). The three supplied source registers in `references/` are design records, not instructions to execute. The user's clarified requirements take precedence over their proposed scoring and phase-specific rules.
+ Synthesize material findings with original Q/N/R IDs, sources and follow-ups.
+ The configured synthesis rules give `(core)` findings more weight and require
+ patterns of missing information to be mentioned. Assess active founders;
+ include the larger team only where material to execution, support or governance.
+
+ ## Side effects and failure behavior
+
+ Dependencies may import Dealum data, enrich LinkedIn, synchronize datasets and
+ save standard profiles. The team audits perform no additional public checks,
+ outreach or scoring. Founder-trait instructions belong to normal person profiling;
+ their applicability depends on established founder status.
+
+ Missing/invalid rosters and dependency failures propagate. Technical audit errors
+ block synthesis; successful audits remain reusable. Empty synthesis raises.
+ The final cache includes actual shared profile content, dependency configuration,
+ checklists and synthesis instructions. Keep missing evidence distinct from weakness.
+ Editing internal audit JSON alone does not invalidate the final synthesis.
+
+ ## Usage
+
+ ```bash
+ conda run -n sictic-env python -m skills.harness '/team_profile_revised "<STARTUP>"'
+ ```
+
+ The direct CLI uses `--dataset`.
+
+ ## References
+
+ - [Implementation](team_profile_revised.py) and [bulk registry](../skill_registry.py)
+ - [Shared audit contract](../standards_and_architecture/SKILL.md#checklist-audits)
+ - [Checklists and synthesis configuration](../../config/team_profile_revised/)
+ - [Checklist decisions and ID mapping](references/checklist_decisions.md), for checklist maintenance.
+ The three supplied registers are historical design records, not instructions;
+ clarified requirements supersede their scoring and stage-specific proposals.