shepaland
- 15 skills
- 0 followers
- 6 hours ago last updated
- ▌ Lexforge · shepalandUse when the user asks for something to be built, added, changed, fixed or looked into in a project and no LexForge change covers it yet - the request names a feature, a bug or a rewrite rather than an artifact of a change that already exists.
- ▌ Lexforge Plan · shepalandUse when a plan, a task list or a breakdown of the work is asked for on a LexForge change that already exists - the user wants the plan for a change or its `tasks.md`, or `lexforge validate` reports a finding in the tasks artifact.
- ▌ Lexforge Spec · shepalandUse when the delta specs of a LexForge change are asked for or have to be fixed - the user wants requirements or scenarios for a change, or `lexforge validate` reports a finding in a delta spec.
- ▌ Lexforge Apply · shepaland bundleUse when every artifact of a LexForge change is written or skipped and the work itself is asked for - the user says to implement the change, to start on `tasks.md`, or to carry on with the next task.
- ▌ Lexforge Debug · shepalandUse when a test fails, a build breaks, a bug is reported or code behaves unexpectedly - before naming a cause or proposing a fix, and again when a fix has already been tried and the problem is still there.
- ▌ Lexforge Design · shepalandUse when the design document of a LexForge change is asked for or has to be reworked - the user wants the design, the decisions or the trade-offs of a change written down, and the change runs on the `spec-driven` schema.
- ▌ Lexforge Verify · shepalandUse when the implementation of a LexForge change looks finished and someone is about to call it done - a verdict is asked for, a completion report is written, or the change is about to be archived.
- ▌ Lexforge Archive · shepalandUse when the verification report of a LexForge change is clean and the change is asked to be closed out - the user says to archive it, to merge its delta into the specs, or to finish the branch it was built on.
- ▌ Lexforge Propose · shepalandUse when the proposal of a LexForge change is asked for or has to be rewritten - the user describes a feature, a fix or a rewrite they want planned, or `lexforge status` shows the `proposal` artifact ready.
- ▌ Sample Plan · shepalandUse when the install mechanics need a skill to copy - stands in for the real planning skill
- ▌ Sample Verify · shepalandUse when the install mechanics need a second skill to copy - stands in for the real verify skill
- ▌ Minimal · shepalandUse when a structure check needs a skill that breaks no rule - the baseline fixture
- ▌
- ▌ No Use When · shepalandRuns the structure checks over a description that opens with the wrong words
- ▌ Future Command · shepalandUse when a command check needs a skill that names a command the CLI does not have