Add tyler/ contributor folder#1
Open
tbrownio wants to merge 2 commits into
Open
Conversation
Mirrors the per-contributor structure introduced by parsa/. Includes .claude/skills (with commit, create-plan, create-spec, discussion, implement, investigate, prepare-pr, release, research-web, review, simple-plan) and the research-dossier-writer agent that create-plan depends on. Notable choices vs my user-level skills: - create-spec is a new skill (no parsa equivalent). Produces a high-level spec with a stateful phases table whose rows each map to a downstream /create-plan invocation. - create-plan merges parsa's mandatory repo audit + brief/dossier reconciliation flow with my new spec-mode (Step 0 auto-detects specs in ./tmp/specs/, picks the next unchecked phase, flips its checkbox, and inherits intent from the spec). - plan_base.md, implement, simple-plan adopted from parsa unchanged (materially richer than my user-level versions: structured Verified Repo Truths sections, Codex executor support, parallel Codex+Claude review). - All other skills are byte-identical between user-level and parsa's, copied as-is. - share-fix not adopted (not in my workflow). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per user direction: this folder should be Tyler's skills as-is, not a merge with parsa's. Reverts create-plan, plan_base.md, implement, and simple-plan to my user-level versions, and removes the research-dossier-writer agent that was only needed by parsa's create-plan flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds a new
tyler/contributor folder mirroring the structure introduced byparsa/. Contains only my skills as-is — no merges with parsa's versions.What's included
tyler/.claude/skills/— full skill set (11 skills), all copied from my user-level~/.claude/skills/:commit,discussion,investigate,prepare-pr,release,research-web,review— byte-identical with parsa'simplement,simple-plan,create-plan(+plan_base.md) — my versions, not parsa'screate-spec(+spec_base.md) — new skill (no parsa equivalent)What
create-specdoesProduces a high-level specification with a stateful phases table whose rows each map to a downstream
/create-planinvocation. Thecreate-planskill detects active specs in./tmp/specs/(Step 0), picks the next unchecked phase, and flips its[ ]→[x]checkbox before writing the plan.Test plan
/create-spec <topic>writes to./tmp/specs/with the correct phases-table column structure (✓ | # | Phase | Goal | Scope | Out of scope | Depends on | Key files / modules | Size)/clear,/create-planwith no args detects the spec, flips the first row's[ ]→[x], and references the spec at the top of the plan file/create-plan "freeform feature description"still works as before (direct mode)🤖 Generated with Claude Code