brief

Name: brief
Availability: InStock
Author: Kicchan

Consolidate Reqord specs, requirements, and design documents into a unified context view.

6|1|Updated Feb 7, 2026

Search Tags:#design #collaboration #context #requirements #specifications #artifact #reqord

Ready to run

npx skills add https://github.com/kicchann/reqord --skill brief-kicchann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/kicchann/reqord/tree/main/plugins/reqord/skills/brief
Command: npx skills add https://github.com/kicchann/reqord --skill brief-kicchann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

spec/req/issueの包括的コンテキストを一括表示して、実装前の状況把握を支援します。複数のアーティファクトを横断して現状を素早く俯瞰できるようにします。

Core Features & Use Cases

Spec/Req/Design.md/Context.yaml/Feedback など、関連する Reqord データを横断的に集約して表示します。
視覚的なつながりと依存関係を一つのビューに統合して、意思決定を迅速化します。
Use Case: 要件・仕様・設計の整合性を事前に確認する際に、関係者全員が最新のコンテキストを共有します。

Quick Start

Ask Reqord to display the comprehensive context for a given spec, req, or issue before starting implementation。

Frequently Asked Questions about brief

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

FAQPage Schema

How do I consolidate end-to-end context for specifications and requirements before implementation?▼

Consolidating end-to-end context for specifications and requirements involves aggregating linked artifacts like spec, req, and design documents into a single unified view. This allows teams to review dependencies and .reqord data comprehensively before implementation.

What is the best way to review linked artifacts across spec and design documents?▼

The best way to review linked artifacts across spec and design documents is to unify them into a single view that visualizes connections and dependencies. This accelerates decision-making by ensuring all stakeholders share the latest context from requirements to feedback.

How do I aggregate Reqord data such as context.yaml and feedback for a unified view?▼

Aggregating Reqord data such as context.yaml and feedback requires reading the linked files and consolidating their contents. This process integrates specifications, requirements, and design.md to present a unified view with actionable insights for the team.

Does this approach work for checking consistency between requirements and design.md files?▼

Yes, checking consistency between requirements and design.md files is a primary application of this approach. It consolidates related Reqord data into one view, allowing stakeholders to visually confirm alignment and dependencies before starting implementation.

When do I need to unify context for specs, requirements, and issues?▼

You need to unify context for specs, requirements, and issues when teams must review linked artifacts before implementing changes across documents. This ensures all stakeholders share the latest context and understand visual dependencies for decision-making.

Can I use a single view to track visual connections and dependencies across design documents?▼

Yes, you can use a single view to track visual connections and dependencies across design documents. Integrating these relationships into one view helps consolidate the comprehensive context and accelerates decision-making before implementation.