Repository navigation
feat(skill): one approval, then onboarding's one question; remove /tskl - #507
Merged
Merged
Conversation
On a blocked preflight the agent sends one message with three remedies, including adding the allow rule itself and handing the user the change when its harness refuses the edit. It no longer asks what the user wants while blocked or after the preflight passes, and a request that names no task goes straight to onboarding. The tskl slash command is removed: init stops installing it, and an upgrade removes the copies an older install recorded.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In a real "let's use taskless" session, the user went through four turns before onboarding asked its one question: a blocked preflight, a failed settings write, a menu of topics, then "set it up". This PR cuts that down to one approval at most, followed by onboarding's question.
Skill
/permissionswithBash(<invocation>:*)in Claude Code). Or the user can approve every Taskless command in chat.agent okpasses. It goes straight to the request.agent onboard./tsklremovedcommandsentry are gone, along with the installer's command writing,buildCommandStub, andwriteCanonicalCommand.commands, so an upgrade deletes thetskl.mdan older install wrote, from.taskless/commands/and from each tool'scommands/tskl/. Empty directories are removed. A tool's other command files are kept, and a symlinkedtskl/is unlinked rather than deleted through. New tests cover each case.init --jsondropscommandsInstalledandwrittenCommands, and keepsremovedCommands. Theinitrecipe goes to topic v6..taskless/README.mdkeeps one stalecommands/line until it's next regenerated. The template is fixed for new installs; a schema migration for one line of docs didn't seem worth it.Spec and release
one-approval-one-questionis archived here. Every scenario that left the specs belonged to a requirement this change removes.remove-tskl-commandis aminorchangeset, because/tsklusers have to change how they ask. The pending release is already minor.agent-ok-preflightis corrected in place, since it is still unreleased.