kspec-observe

Convert observations into tasks or inbox items via kspec meta observe.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-observe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kspec-observe
Source: https://github.com/lepahc/kynetic-spec/tree/main/.agents/skills/kspec-observe
Command: npx skills add https://github.com/lepahc/kynetic-spec --skill kspec-observe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observations capture systemic patterns such as friction, successes, questions, and ideas, turning informal feedback into a structured loop that informs process improvement and better work planning.

Core Features & Use Cases

  • Record and categorize observations by type (friction, success, question, idea) for cross-session visibility.
  • Review, triage, and promote observations to tasks or inbox items to drive concrete work.
  • Link observations to workflows and historical context to guide continuous improvement.

Quick Start

Capture a friction observation for your current workflow by running kspec meta observe friction 'describe the issue'.

Frequently Asked Questions about kspec-observe

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

FAQPage Schema
How do I capture systemic patterns from workflow observations to improve processes?

You capture systemic patterns by logging friction, successes, questions, and ideas as structured observations across sessions. This converts informal workflow feedback into categorized records that inform continuous process improvement and better work planning.

What is the best way to turn informal feedback into actionable work items?

The best way to turn informal feedback into actionable work items is to record it as categorized observations, then review and triage them. You promote observations into tasks or inbox items, linking them to workflows for historical context.

How do I log friction and successes across multiple sessions for task triage?

You log friction and successes across sessions by categorizing observations for cross-session visibility. The system relies on meta observe commands to create artifacts, which you then triage and promote into concrete tasks or inbox items.

Can I categorize process improvement observations by type for better visibility?

Yes, you can categorize process improvement observations by type, specifically friction, success, question, and idea. This categorization provides cross-session visibility to help structure feedback and guide continuous workflow improvements.

How do I promote an observation into a task within a structured workflow?

You promote an observation into a task by using meta observe commands to review and triage captured artifacts. This action converts the recorded friction, question, or idea into a concrete work item within your structured workflow.