All authors
Claude Skills by rayedbajwa
github.com/rayedbajwa10 skills0 installs3 views
- Speckit AnalyzeUser input (consider it if not empty): $ARGUMENTS **Read-only**: change no files. The constitution (`.specify/memory/constitution.md`) is non-negotiable: a conflict with it is always CRITICAL and is fixed in spec, plan or tasks, never by reinterpreting the principle.Votes: 0GitHub stars: 3
- Speckit ChecklistChecklist focus (consider it if not empty): $ARGUMENTS A checklist tests whether the **requirements are well written** — complete, clear, consistent, measurable, covering the scenarios — not whether the implementation works. - ✅ "Is 'prominent display' quantified with specific sizing? [Clarity, Spec §FR-4]" - ✅ "Are error responses specified for every failure mode? [Completeness, Gap]" - ❌ "Verify the button works" / "Test error handling" / "Confirm the API returns 200"Votes: 0GitHub stars: 3
- Speckit ClarifyUser input (consider it if not empty): $ARGUMENTS Goal: find the ambiguities and missing decisions in the active spec that would change the plan or tests, ask about the most important ones (at most 5 questions), and write the answers into the spec.Votes: 0GitHub stars: 3
- Speckit ConstitutionPrinciples input (consider it if not empty): $ARGUMENTS Work on `.specify/memory/constitution.md` in place (never a new file). It may still hold template tokens like `[PROJECT_NAME]` or `[PRINCIPLE_1_NAME]`.Votes: 0GitHub stars: 3
- Speckit ImplementUser input (consider it if not empty): $ARGUMENTSVotes: 0GitHub stars: 3
- Speckit InitInput: $ARGUMENTS Spaces sets up `.specify/` when the project is onboarded, so this is normally a check. 1. Find the repository root (`git rev-parse --show-toplevel`). Not a git repository: run `git init` there first. 2. If `.specify/` exists, list its top level, say it is already initialized, and stop. 3. Otherwise copy the templates and make the scripts executable: ```bash root="$(git rev-parse --show-toplevel)" cp -r "SPECKIT_ROOT/specify-templates/." "$root/.specify/" chmod +x "$root/.spe...Votes: 0GitHub stars: 3
- Speckit PlanPlanning input (consider it if not empty): $ARGUMENTSVotes: 0GitHub stars: 3
- Speckit SpecifyFeature description (the user's input; use it, never ask for it again): ```text $ARGUMENTS ```Votes: 0GitHub stars: 3
- Speckit TasksContext (consider it if not empty): $ARGUMENTSVotes: 0GitHub stars: 3
- Speckit TaskstoissuesUser input (consider it if not empty): $ARGUMENTS 1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` and take the tasks path. 2. Get the remote: `git config --get remote.origin.url`. **Continue only if it is a GitHub URL.** 3. For each task in tasks.md, in dependency order, create an issue in **that repository only** — never in any repository that does not match the remote — with the task ID and description as the title, and its phase, story and depen...Votes: 0GitHub stars: 3