pms-query

Answer project questions by consulting wiki documents and citing source references.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ag3nt3154/Driverless_AGI --skill pms-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pms-query
Source: https://github.com/ag3nt3154/Driverless_AGI/tree/main/projects/project_management_system/.dagi/skills/pms-query
Command: npx skills add https://github.com/ag3nt3154/Driverless_AGI --skill pms-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Answering project questions by consulting the wiki and tracing back to source documents to ensure every claim is grounded in official project records rather than memory.

Core Features & Use Cases

  • Grounded wiki reasoning: answer queries about schedules, features, decisions, and deliverables using wiki content.
  • Cross-document correlation: synthesize information from multiple wiki files to provide complete, coherent answers.
  • Source tracing: attach exact wiki sections and linked sources to support every claim for auditability.

Quick Start

Ask a project question and let the agent ground the answer in the wiki and linked sources.

Frequently Asked Questions about pms-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I answer project management questions using wiki documentation?

Answer project management questions by consulting the wiki to ground responses in official documentation. The Skill queries wiki files, quotes relevant sections, and cites exact sources to ensure every status, decision, or deliverable claim is traceable and auditable.

What is cross-document query resolution for project wikis?

Cross-document querying synthesizes information from multiple wiki files to provide complete answers. It correlates schedules, features, and decisions across the project wiki, ensuring coherent responses that cite exact sections and linked sources for auditability.

Can I trace project decisions back to their source documents in the wiki?

Source tracing attaches exact wiki sections and linked references to every answer. When querying project decisions or deliverables, the Skill quotes the relevant documentation portions, grounding each claim in official project records rather than memory.

Do I need an initialized wiki to query project status and deliverables?

An initialized and accessible wiki is required to query project status and deliverables. The Skill depends on existing wiki documents to extract answers, quote relevant sections, and cite sources, meaning it cannot function without a populated project wiki environment.

What's the best way to ground project schedule answers in wiki evidence?

The best way to ground schedule answers is querying the wiki directly and extracting exact quotes from relevant documents. This approach correlates schedule information across files, providing responses backed by cited wiki sections rather than relying on personal recall.

Why does my project wiki query return ungrounded answers without source citations?

Wiki queries return ungrounded answers when the project wiki is not properly initialized or accessible. The Skill requires a populated wiki environment to trace source references and attach exact document sections to support every claim it generates.