cash-ask

Query project-local openspec documentation using deterministic lexical search.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-ask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cash-ask
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-ask
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reliable, grounded way to query project-specific documentation and specifications without relying on potentially outdated or hallucinated training data.

Core Features & Use Cases

  • Deterministic Search: Performs lexical matching against the openspec/ directory to ensure answers are based on current project truth.
  • Context-Aware Retrieval: Prioritizes main specifications over historical archives to provide accurate implementation details.
  • Use Case: When a developer needs to understand the design rationale behind a specific feature or verify how a component functions, they can query the documentation directly to get an authoritative answer.

Quick Start

Use the cash-ask skill to search for the design specifications of the activity-bar badge component.

Frequently Asked Questions about cash-ask

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

FAQPage Schema
How do I query project specifications and documentation locally without hallucination?

You can query project specifications using deterministic lexical search against the openspec directory, which performs grounded information extraction from local files to ensure answers reflect current project truth rather than outdated training data.

How do I search the openspec directory for feature design verification?

Searching the openspec directory for feature design verification uses lexical matching to retrieve context-aware specifications, prioritizing main specifications over historical archives to provide accurate implementation details for the queried component.

Does the documentation search require git to detect the repository root?

Yes, documentation search requires git for repository root detection, and also needs local file system access to perform grounded information extraction and retrieve specifications from the project's openspec directory.

What is the best way to track historical changes in project specifications?

The best way to track historical changes in project specifications is using context-aware retrieval that prioritizes main specifications over historical archives, applying lexical matching within the openspec directory to trace design rationale and modifications.

Why does lexical search prioritize main specifications over historical archives?

Lexical search prioritizes main specifications over historical archives to provide accurate implementation details and context-aware retrieval, ensuring developers receive current project truth when querying design rationale or verifying component functionality.