tasleemat

Files (200)

• bug_report.yml · .github/ISSUE_TEMPLATE/
• config.yml · .github/ISSUE_TEMPLATE/
• new_form_request.yml · .github/ISSUE_TEMPLATE/
• translation_improvement.yml · .github/ISSUE_TEMPLATE/
• PULL_REQUEST_TEMPLATE.md · .github/
• ci.yml · .github/workflows/
• deploy-docs.yml · .github/workflows/
• publish-mcp.yml · .github/workflows/
• .gitignore
• CHANGELOG.md
• CODE_OF_CONDUCT.md
• CONTRIBUTING.md
• CONTRIBUTING_AR.md
• LICENSE
• README.md
• README_AR.md
• RELEASE_NOTES.md
• SECURITY.md
• SKILL.md
• TECHNICAL.md
• TECHNICAL_AR.md
• _config.yml
• 66631fc7bc5a4c4c91bf53e0e074c0aa.json · _stitch_designs/screens/
• 66631fc7bc5a4c4c91bf53e0e074c0aa_actual.html · _stitch_designs/screens/
• 80e3594dd2de4c31a6b3f5ddd4bed3b5.json · _stitch_designs/screens/
• 80e3594dd2de4c31a6b3f5ddd4bed3b5_actual.html · _stitch_designs/screens/
• d5a82735c4a448e9962ccd685a4394ed.json · _stitch_designs/screens/
• d5a82735c4a448e9962ccd685a4394ed_actual.html · _stitch_designs/screens/
• f3e5b34906a04a2eb2c99a7262a48939.json · _stitch_designs/screens/
• f3e5b34906a04a2eb2c99a7262a48939_actual.html · _stitch_designs/screens/
• f699bea80c2c4c0dab54430a6b8e8378.json · _stitch_designs/screens/
• f699bea80c2c4c0dab54430a6b8e8378_actual.html · _stitch_designs/screens/
• fe772f47175f48ab924c1b977d680f4a.json · _stitch_designs/screens/
• fe772f47175f48ab924c1b977d680f4a_actual.html · _stitch_designs/screens/
• screen1_80e3594dd2de4c31a6b3f5ddd4bed3b5.html · _stitch_designs/screens/
• screen1_preview.png · _stitch_designs/screens/
• screen2_66631fc7bc5a4c4c91bf53e0e074c0aa.html · _stitch_designs/screens/
• screen2_preview.png · _stitch_designs/screens/
• screen3_f699bea80c2c4c0dab54430a6b8e8378.html · _stitch_designs/screens/
• screen3_preview.png · _stitch_designs/screens/
• screen4_f3e5b34906a04a2eb2c99a7262a48939.html · _stitch_designs/screens/
• screen4_preview.png · _stitch_designs/screens/
• screen5_fe772f47175f48ab924c1b977d680f4a.html · _stitch_designs/screens/
• screen5_preview.png · _stitch_designs/screens/
• screen6_d5a82735c4a448e9962ccd685a4394ed.html · _stitch_designs/screens/
• screen6_preview.png · _stitch_designs/screens/
• CHANGELOG.npy · _tokens/
• CODE_OF_CONDUCT.npy · _tokens/
• CONTRIBUTING.npy · _tokens/
• CONTRIBUTING_AR.npy · _tokens/
• README.npy · _tokens/
• README_AR.npy · _tokens/
• SECURITY.npy · _tokens/
• LEXICON.npy · _tokens/docs/
• README.npy · _tokens/docs/
• README_AR.npy · _tokens/docs/
• 01_getting_started.npy · _tokens/docs/ar/
• 02_usage_guide.npy · _tokens/docs/ar/
• 03_pmo_policy_manual.npy · _tokens/docs/ar/
• 04_stage_gates_and_governance.npy · _tokens/docs/ar/
• …and 140 more

SKILL.md (first lines)

# Tasleemat: Bilingual Project Deliverable Assistant

Help users find, understand, and use Tasleemat project-management
artifacts in Arabic or English.

Keep this skill limited to artifact discovery, retrieval, drafting,
structural validation, and supported rendering.

## When to use

Use this skill when the user asks to:
- Find a Tasleemat artifact or template.
- Prepare a draft using an existing Tasleemat template.
- Understand how to fill a deliverable.
- Inspect an illustrative example or field dictionary.
- Validate a supported completed-data payload.
- Retrieve bilingual terminology.
- Use the Tasleemat Python library or MCP interface.

Do not treat this skill as an autonomous PMO, approval authority,
standards certification service, or complete methodology engine.

## 1. Check available access

Use the access method already available:

1. Connected Tasleemat MCP tools.
2. An installed Tasleemat Python package.
3. Repository assets and documentation.

Verify the available version, public interfaces, and artifact metadata
before relying on them.

Do not assume this SKILL.md file includes the full repository,
templates, examples, schemas, or an executable server.

If the required assets or capabilities are unavailable:
- Explain what is missing.
- Ask for the relevant artifact, repository access, or configured tool.
- Do not invent Tasleemat content.
- Do not automatically install packages, run remote scripts, or connect
  services without authorization.

## 2. Identify the task

Establish:
- Requested deliverable or project-management task.
- Output language: Arabic or English.
- Available project facts and evidence.
- Intended output: explanation, template, draft, structured data,
  validation report, or rendered document.

Use existing conversation context.
Ask only for information that materially affects the result.

If the user is unsure which artifact is appropriate, search the
catalog and explain the relevant options briefly.

Do not assign governance authority or mandatory policy thresholds
without an adopted organizational source.

## 3. Discover and retrieve the artifact

Use a verified artifact ID from the catalog.

Retrieve only the assets needed:
- Template: document structure.
- Guide: writing instructions.
- Example: illustrative reference, not project evidence.
- Dictionary: field descriptions.
- Form-definition JSON: structured field metadata.
- Companion completed-data schema: validation contract, where supported.

Do not assume a JSON asset returned with role "schema" is the
companion completed-data JSON Schema.

Verify its purpose before using it for validation or tool parameters.

Do not load the entire artifact library unnecessarily.

## 4. Prepare the draft

Follow the retrieved template and relevant guide.

- Preserve its section structure unless the user requests a separate,
  clearly identified adaptation.
- Use supplied facts and evidence.
- Separate facts, assumptions, and missing information.
- Use explicit placeholders for unknown values.
- Do not invent dates, budgets, stakeholder identities, metrics,
  decisions, signatures, or approvals.
- Do not copy fictional example values into the user's project as facts.
- Do not present a generated document as already approved.

Create outputs in a separate project workspace or return them in chat.

Never overwrite source forms or installed package assets.

## 5. Validate supported structured data

Use Tasleemat's public validator when available.

Before validation:
- Confirm the artifact ID.
- Check completed-data schema availability.
- Confirm the requested definition reference, if supplied.
- Use the documented strict or draft mode.

Distinguish:
- Valid structured data.
- Invalid structured data.
- Validation unavailable.
- Unsupported definition or schema capability.
- Validation execution failure.

Do not report a successful check when validation did not run.

Preserve:
- Artifact ID.

From fakhruldeen/Tasleemat, MIT.

More from fakhruldeen/Tasleemat