1.8 KiB
Prompt
Move the fix out of the root checkout into an isolated worktree and include a Piker-specific clearing, accounting, order-control, and trade-ledger expert skill in the worktree’s commit plan. Use a cross-harness, AI-provider-neutral standard location for its canonical files instead of making one provider directory authoritative.
Response summary
Created a portable piker-clearing-expert skill bundle under the provider-neutral .agents/skills/ convention, with a relative Claude compatibility link. It covers subsystem ownership, protocols, identities, persistence, backend variation, debugging hazards, and test strategy. Added the canonical wkts/ runtime ignore.
Files changed
.gitignore- ignores the canonical root-level worktree directory..agents/skills/piker-clearing-expert/SKILL.md- core expertise..agents/skills/piker-clearing-expert/architecture.md- deep flows..agents/skills/piker-clearing-expert/gotchas.md- diagnosis..agents/skills/piker-clearing-expert/test-map.md- test map..claude/skills/piker-clearing-expert- relative Claude bridge.ai/README.md- defines the provider-neutral source convention.ai/claude-code/README.md- advertises the shared skill to Claude.ai/opencode/README.md- advertises the shared skill to OpenCode.
Human edits
The human rejected planning in the dirty root checkout, required a dedicated worktree, expanded the work to include a durable expert skill, and then directed its canonical source into a cross-provider standard location. The agent applied those directed scope and layout changes; no direct manual source edit was identified.