All authors
Claude Skills by Langerrr
github.com/Langerrr13 skills0 installs35 views
- Async ReasoningThis skill should be used when implementing or designing code with async data flows — "state management design", "async data flow", "stale data", "cache invalidation", "optimistic update", "init order", "race condition", "write then read", "data not updating", "cache not refreshing", "UI shows old data after save", "value doesn't update", "empty data on first load". Also applicable when working with caching layers, event-driven systems, or any code where write and read paths have different la...Votes: 0GitHub stars: 10
- RetroThis skill should be used when the user asks to "retro", "evaluate zforge", "review plugin performance", "score this session", or wants to assess how well zforge's workflow served a feature. Evaluates zforge's workflow scaffolding, not the project's technical decisions or LLM reasoning quality.Votes: 0GitHub stars: 10
- Template ConventionsThis skill should be used when the user asks to "plan a feature", "what goes in the phase file", "which file owns this", "what evidence class is this", "how do I verify a claim no test can settle", "where should this doc go", or when writing, reading or updating any zforge feature document under docs/{feature}/. Provides the template structure, file ownership rules, the two-axis evidence scale for what was executed and what was judged, phase states, and naming conventions.Votes: 0GitHub stars: 10
- Feature ExecutionThis skill should be used when the user asks to "orchestrate the feature", "run the phases", "resume implementation", "continue the plan", "the phase agent died", "the agent stopped on its usage limit", "accept this phase", "can these phases run in parallel", "is this phase done", "does this shortfall matter", or "should I flag this or accept it" — and whenever the zforge feature-orchestrate or feature-resume workflow executes. Use it as well when a phase reported done but its evidence was ne...Votes: 0GitHub stars: 10
- Acceptance AgentUse this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include $zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the phase's ## Evidence Required rows against their artifacts, re-executes what a fact forces or its own judgment selects, and returns an achieved-class table with a per-row verdict...Votes: 0GitHub stars: 10
- DebugRoute a concrete reproducible failure through the installed debugging skills; not for open-ended exploration.Votes: 0GitHub stars: 10
- Feature OrchestrateExecute an existing zforge feature plan autonomously with phase subagents and evidence-based acceptance.Votes: 0GitHub stars: 10
- Feature ResumeResume an existing zforge feature plan interactively, implementing and accepting one phase at a time.Votes: 0GitHub stars: 10
- Phase AgentUse this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include $zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See "When to invoke" in the agent body for worked scenarios. Do not use it for work with no phase file — it reads its instructions from one.Votes: 0GitHub stars: 10
- Plan StatusSummarize all zforge feature plans, phase counts, and standing flags in the current workspace.Votes: 0GitHub stars: 10
- PlanPlan a feature with zforge's completeness contract and write the appropriate requirements or implementation artifact tree.Votes: 0GitHub stars: 10
- ReviewCheck implementation against an existing zforge feature ledger; not for general code review.Votes: 0GitHub stars: 10
- TrackShow one zforge feature's phase progress, evidence gaps, standing flags, and open decisions.Votes: 0GitHub stars: 10