Skip to main content
Project Intelligence

Skill Library

Project Intelligence is not a chat — it is a set of specialized competencies that we call Skills. Each skill represents a strictly defined working methodology, packaged as a set of instructions and tools.

Instead of trying to be a "jack of all trades", the system uses the skills that are needed depending on the stage of your project and the current task.

Catalog of capabilities by project stage​

Below is the complete list of skills, broken down by the phases of the project lifecycle.

1. Orientation and project context​

Before starting work, the system gets oriented in your environment and methodology.

  • Environment setup (/environment): binding the task tracker and the document-management system, the methodology, and the project boundaries.
  • Document registry (/documents): registration and classification of project documents: charter, scope boundaries, BRD, risk register.
  • Next-step advisor (/path): determines the current stage of the project and suggests which tool to apply next.

2. Initiation and requirements​

At this stage the AI helps turn scattered stakeholder ideas into a clear technical document.

  • Project initiation (/initiate): creating the project charter and defining the key goals.
  • Contract analysis (/contract-review): analysis of the delivery contract: scope of work, deadlines, and risk candidates.
  • Scope definition (/scope): a clear demarcation of what is in the project and what is not, to prevent uncontrolled growth of the scope of work.
  • Requirements collection (/requirements): starting the BRD: the seed, structure, and skeleton of the document.
  • Requirements elicitation (/elicit): analysis of meetings, correspondence, and documents for extracting all explicit and implicit business needs.
  • Working through decisions (/question): breaking down open questions and unresolved decisions in the BRD and specifications.
  • Specification (/specify): transforming raw requirements into structured specifications, user stories, and acceptance criteria.

3. Planning and organization​

Translating requirements into a concrete action plan and task structure.

  • Task structure creation (/tickets): automatic generation of the task hierarchy in the system (epics → user stories → tasks).
  • Effort estimation (/estimate): calculating the effort and the resources required to implement each task.
  • Planning (/plan): building the work schedule, defining stages (milestones), sprints, and releases.
  • Meeting agenda (/meeting-agenda): the date and the agenda of a meeting with specific participants — based on the facts of the project, not on templates.

4. Operational management and control​

Maintaining order in the project and ensuring the transparency of processes.

  • Operational management (/manage): a day-to-day walk-through: work in progress, schedule, board, sprint, and the upcoming periods.
  • Scope check (/scope-check): assumptions of approved scope, early capture of creep / OOS / volume breach, change register, and a draft client notice. For PMs and portfolio managers; do not confuse with /scope (writing the scope statement).
  • Risk register (/risks): identification, assessment, and review of the project's delivery risks.
  • Risk actions (/risk-mitigate): mitigation measures and a response plan for confirmed risks.

5. Monitoring and reporting​

Objective analysis of results and communication with management.

  • Status snapshot (/status-snapshot): a dated snapshot of work and plans — the basis for comparing periods.
  • Budget snapshot (/budget-snapshot): a dated snapshot of the budget and actual expenditures.
  • Change analysis (/status-delta): comparison with the previous snapshot: what is new, what has changed, what is closed, and what is under observation.
  • Delivery quality (/quality): phase methodology evidence audit (artefacts, decisions, readiness) and a gap action plan. For PMO; does not replace the status report (/report) and is not a work inventory.
  • Report formatting (/report-format): configuring report templates and structure to the requirements of specific stakeholders.
  • Status reporting (/report): generation of objective reports on project progress based on facts, with links to sources; with a template available — the report is rendered into a presentation (.pptx), edited directly in the slides.

Skills are grouped under the working scenarios of the system's users — project managers and administrators, analysts, portfolio managers, PMO, and senior management. Details: Specialist roles.

How skills work in the system​

You can interact with skills in two ways:

1. Manual launch​

You choose the tool you need from the skill menu (by typing / in the chat). This is useful when you know exactly what result you need (for example, "I need a report").

2. Automatic activation​

This is the main working mode. Project Intelligence analyzes your request and the project context. If it understands that a chain of skills is needed for a quality answer, it activates them automatically, without making you switch modes manually.

Example: Request: "Why are we not making it in time for the release of module X?" → the system uses universal search to find the facts, automatically engages the /manage and /risks skills (to find the cause of the delay and assess the risks), and compares the current state with the last /status-snapshot snapshot to show the scale of the deviation.