[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C7EXRK3QNN3E1GRGAVHMVG":3,"skill-same:01M6C7EXRK3QNN3E1GRGAVHMVG":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M6C7EXRK3QNN3E1GRGAVHMVG","kspec-observe",null,"Capture and act on systemic patterns — friction, successes, questions, and ideas. The feedback loop that drives process improvement.","lepahc\u002Fkynetic-spec","lepahc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255431765?v=4","01M6C7E6Z0C8SE1X6PJ2F9Q1CX","01M6C7E744QKNYBVZ7KV7Z69GF",1,"MIT","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkspec-observe\u002FSKILL.md",[],[18,19,20,21,22,23,24],"observe","kspec observe","loop","feedback","capture","process","friction","2026-11-10 10:12:30",false,"---\nname: kspec-observe\ndescription: Capture and act on systemic patterns — friction, successes,\n  questions, and ideas. The feedback loop that drives process improvement.\n---\n\u003C!-- kspec-managed -->\n# Observations\n\nCapture and act on systemic patterns — friction, successes, questions, and ideas. Observations are the feedback loop that drives process improvement.\n\n## When to Use\n\n- You hit friction (something harder than it should be)\n- You notice a success worth replicating\n- A systemic question arises (not session-specific)\n- An improvement idea surfaces during work\n\n**Not for:** Session-local questions (use `kspec meta question`), future work items (use `kspec inbox add`), or task-specific notes (use `kspec task note`).\n\n## Observation Types\n\n| Type       | When to use                           | Example                                              |\n| ---------- | ------------------------------------- | ---------------------------------------------------- |\n| `friction` | Something is harder than it should be | \"Bulk updates require too many commands\"             |\n| `success`  | A pattern that worked well            | \"Dry-run before derive prevented duplicate tasks\"    |\n| `question` | A systemic question about process     | \"When should agents use inbox vs tasks?\"             |\n| `idea`     | An improvement opportunity            | \"CLI could suggest next steps after task completion\" |\n\n## Capturing Observations\n\nCapture in the moment — don't wait until later. The value is in the raw context.\n\n```bash\n# Friction: something was harder than it should be\nkspec meta observe friction \"Had to run 5 commands to update one spec field\"\n\n# Success: a pattern worth remembering\nkspec meta observe success \"Using --dry-run before derive prevented duplicate tasks\"\n\n# Question: systemic, not session-local\nkspec meta observe question \"When should agents enter plan mode vs just implement?\"\n\n# Idea: something that could improve the system\nkspec meta observe idea \"CLI could suggest next steps after task completion\"\n\n# Link to a workflow for context (use a workflow ref defined in the project)\nkspec meta observe friction \"Workflow step lost context unexpectedly\" --workflow @\u003Cworkflow-id>\n```\n\n## Reviewing Observations\n\n```bash\n# All unresolved observations (default)\nkspec meta observations\n\n# Only those awaiting resolution\nkspec meta observations --pending-resolution\n\n# Filter by type\nkspec meta observations --type friction\n```\n\n## Acting on Observations\n\n### Promote to Task\n\nWhen an observation reveals clear, actionable work:\n\n```bash\nkspec meta promote @ref --title \"Add bulk AC command\" --priority 2\n```\n\n### Resolve\n\nWhen addressed, documented, or no longer relevant:\n\n```bash\n# Single observation with resolution note\nkspec meta resolve @ref \"Addressed by the recent change to the affected workflow\"\n\n# Batch resolve related observations\nkspec meta resolve --refs @ref1 @ref2 @ref3 --resolution \"All addressed by new workflow\"\n```\n\n### Convert from Inbox\n\nWhen an inbox item is really a pattern observation, not future work:\n\n```bash\nkspec meta observe --from-inbox @inbox-ref\nkspec meta observe --from-inbox @inbox-ref --type friction\n```\n\n## Decision Flow\n\n```\nWhen you notice something during work:\n├── Is it future work?\n│   └── Yes → kspec inbox add \"...\"\n├── Is it about THIS task only?\n│   └── Yes → kspec task note @task \"...\"\n└── Is it a systemic pattern?\n    └── Yes → kspec meta observe \u003Ctype> \"...\"\n```\n\n```\nFor each pending observation:\n├── Still relevant?\n│   ├── No → resolve with note\n│   └── Yes → Needs action?\n│       ├── No (just learning) → document and resolve\n│       └── Yes → Scope clear?\n│           ├── Yes → promote to task\n│           └── No → add to inbox for later triage\n```\n\n## Where Observations Fit\n\n| What you have             | Where                   | Why                                |\n| ------------------------- | ----------------------- | ---------------------------------- |\n| Vague idea for future     | `inbox add`             | Low-friction capture, triage later |\n| Clear actionable work     | `task add`              | Ready to implement                 |\n| Something was hard        | `meta observe friction` | Informs process improvement        |\n| Something worked well     | `meta observe success`  | Worth replicating                  |\n| Session-local question    | `meta question add`     | Track during current session       |\n| Systemic process question | `meta observe question` | Broader than one session           |\n\n## Batch Capture\n\nWhen capturing multiple observations at once (e.g., during reflection), use `kspec batch`:\n\n```bash\nkspec batch --commands '[\n  {\"command\":\"meta observe\",\"args\":{\"type\":\"friction\",\"content\":\"Bulk updates require too many commands\"}},\n  {\"command\":\"meta observe\",\"args\":{\"type\":\"success\",\"content\":\"Dry-run before derive prevented duplicates\"}}\n]'\n```\n\n## Integration\n\n- **`$kspec-triage observations`** — Processes pending observations during triage\n- **`$kspec-reflect`** — Creates observations from session learnings\n- **`kspec session start`** — Shows pending observation count\n","\u003C!-- kspec-managed -->\n# Observations\n\nCapture and act on systemic patterns — friction, successes, questions, and ideas. Observations are the feedback loop that drives process improvement.\n\n## When to Use\n\n- You hit friction (something harder than it should be)\n- You notice a success worth replicating\n- A systemic question arises (not session-specific)\n- An improvement idea surfaces during work\n\n**Not for:** Session-local questions (use `kspec meta question`), future work items (use `kspec inbox add`), or task-specific notes (use `kspec task note`).\n\n## Observation Types\n\n| Type       | When to use                           | Example                                              |\n| ---------- | ------------------------------------- | ---------------------------------------------------- |\n| `friction` | Something is harder than it should be | \"Bulk updates require too many commands\"             |\n| `success`  | A pattern that worked well            | \"Dry-run before derive prevented duplicate tasks\"    |\n| `question` | A systemic question about process     | \"When should agents use inbox vs tasks?\"             |\n| `idea`     | An improvement opportunity            | \"CLI could suggest next steps after task completion\" |\n\n## Capturing Observations\n\nCapture in the moment — don't wait until later. The value is in the raw context.\n\n```bash\n# Friction: something was harder than it should be\nkspec meta observe friction \"Had to run 5 commands to update one spec field\"\n\n# Success: a pattern worth remembering\nkspec meta observe success \"Using --dry-run before derive prevented duplicate tasks\"\n\n# Question: systemic, not session-local\nkspec meta observe question \"When should agents enter plan mode vs just implement?\"\n\n# Idea: something that could improve the system\nkspec meta observe idea \"CLI could suggest next steps after task completion\"\n\n# Link to a workflow for context (use a workflow ref defined in the project)\nkspec meta observe friction \"Workflow step lost context unexpectedly\" --workflow @\u003Cworkflow-id>\n```\n\n## Reviewing Observations\n\n```bash\n# All unresolved observations (default)\nkspec meta observations\n\n# Only those awaiting resolution\nkspec meta observations --pending-resolution\n\n# Filter by type\nkspec meta observations --type friction\n```\n\n## Acting on Observations\n\n### Promote to Task\n\nWhen an observation reveals clear, actionable work:\n\n```bash\nkspec meta promote @ref --title \"Add bulk AC command\" --priority 2\n```\n\n### Resolve\n\nWhen addressed, documented, or no longer relevant:\n\n```bash\n# Single observation with resolution note\nkspec meta resolve @ref \"Addressed by the recent change to the affected workflow\"\n\n# Batch resolve related observations\nkspec meta resolve --refs @ref1 @ref2 @ref3 --resolution \"All addressed by new workflow\"\n```\n\n### Convert from Inbox\n\nWhen an inbox item is really a pattern observation, not future work:\n\n```bash\nkspec meta observe --from-inbox @inbox-ref\nkspec meta observe --from-inbox @inbox-ref --type friction\n```\n\n## Decision Flow\n\n```\nWhen you notice something during work:\n├── Is it future work?\n│   └── Yes → kspec inbox add \"...\"\n├── Is it about THIS task only?\n│   └── Yes → kspec task note @task \"...\"\n└── Is it a systemic pattern?\n    └── Yes → kspec meta observe \u003Ctype> \"...\"\n```\n\n```\nFor each pending observation:\n├── Still relevant?\n│   ├── No → resolve with note\n│   └── Yes → Needs action?\n│       ├── No (just learning) → document and resolve\n│       └── Yes → Scope clear?\n│           ├── Yes → promote to task\n│           └── No → add to inbox for later triage\n```\n\n## Where Observations Fit\n\n| What you have             | Where                   | Why                                |\n| ------------------------- | ----------------------- | ---------------------------------- |\n| Vague idea for future     | `inbox add`             | Low-friction capture, triage later |\n| Clear actionable work     | `task add`              | Ready to implement                 |\n| Something was hard        | `meta observe friction` | Informs process improvement        |\n| Something worked well     | `meta observe success`  | Worth replicating                  |\n| Session-local question    | `meta question add`     | Track during current session       |\n| Systemic process question | `meta observe question` | Broader than one session           |\n\n## Batch Capture\n\nWhen capturing multiple observations at once (e.g., during reflection), use `kspec batch`:\n\n```bash\nkspec batch --commands '[\n  {\"command\":\"meta observe\",\"args\":{\"type\":\"friction\",\"content\":\"Bulk updates require too many commands\"}},\n  {\"command\":\"meta observe\",\"args\":{\"type\":\"success\",\"content\":\"Dry-run before derive prevented duplicates\"}}\n]'\n```\n\n## Integration\n\n- **`$kspec-triage observations`** — Processes pending observations during triage\n- **`$kspec-reflect`** — Creates observations from session learnings\n- **`kspec session start`** — Shows pending observation count\n",{"name":5,"description":7},"main","c4b0de3035f8512bba7eb0a9b4e39ea2fbd3f08e",".agents\u002Fskills\u002Fkspec-observe",2,"https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec","https:\u002F\u002Fgithub.com\u002Flepahc","2026-07-22 18:57:40",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add lepahc\u002Fkynetic-spec --skill kspec-observe",{"tool":43,"command":44},"bunx","bunx skills add lepahc\u002Fkynetic-spec --skill kspec-observe",{"tool":46,"command":47},"pnpm","pnpm dlx skills add lepahc\u002Fkynetic-spec --skill kspec-observe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkspec-observe\u002FSKILL.md",true,[],[52,70,76,84,95,103],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":67,"publishedAt":25},"01M6C7KCZE43MDZ74FV3A5TDCQ","writing-specs","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwriting-specs\u002FSKILL.md",[57,62],{"categoryNo":58,"categoryName":59,"taxonomyType":60,"taxonomyTypeDesc":61},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[68,69],"writing","writing specs",{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":25},"01M6C7KAK9CBJ87PX3BCW7B7YG","triage","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftriage\u002FSKILL.md",[],[72],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":25},"01M6C7K89VN6FJCT8M86K56EE8","triage-inbox","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftriage-inbox\u002FSKILL.md",[],[72,82,83],"inbox","triage inbox",{"skillNo":85,"name":86,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":25},"01M6C7K6F2342AC1TJCN9PM0ZB","triage-automation","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftriage-automation\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":60,"taxonomyTypeDesc":61},"01JBSEEDCAT000000000000023","Skill与智能体开发",[72,93,94],"automation","triage automation",{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":25},"01M6C7K3TFQ88QQBW3PXYDHQG2","task-work","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftask-work\u002FSKILL.md",[],[101,102],"work","task work",{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":25},"01M6C7K168CH3XJCC3PDGA9H6C","review","https:\u002F\u002Fgithub.com\u002Flepahc\u002Fkynetic-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Freview\u002FSKILL.md",[],[105]]