All authors
Claude Skills by congdang-agilityio
github.com/congdang-agilityio12 skills0 installs0 views
- GradersNo description providedVotes: 0GitHub stars: 2
- BaTurn a product idea or requirement sources (files, links, a chat description) into signed-off requirements and small user stories in the Backlog: analyze, ask clarifying questions until the BA declares them clear, get requirement sign-off (GATE 1), draft PRD and stories, get story approval (GATE 2), publish epic and stories. Use when the stakeholder brings a new feature or product idea, shares requirement documents, answers clarifying questions, or changes requirements mid-stream.Votes: 0GitHub stars: 2
- DeployDevOps procedure, with the Railway CLI under the stakeholder's own login (no tokens): release a milestone (deploy gate, release notes, deploy and smoke-test staging, request GATE 3 on GitHub; after approval deploy production, publish, mark items Released); change the platform for an infra task (databases, variables, service settings) with approval for production; read logs and deployments; roll back production after approval. On a failed deploy or smoke test, file a P0 bug with the logs. Use ...Votes: 0GitHub stars: 2
- DevDeveloper procedure: implement exactly one task issue with TDD in its own git worktree, keep the change within the task's size, and open a small PR; or rework a PR after review/QA feedback; or rebase a PR labeled needs-rebase. Use when a task in Todo is dispatched to a developer slot, when review or QA sends a task back, or when a PR conflicts with main.Votes: 0GitHub stars: 2
- DoctorDiagnose why squad cannot run in this repository: tools, gh login and token scopes, .squad/config.yml and its board ids, board fields and Status columns, items missing from GitHub's item listing, labels, conflicting project workflows, merge settings, branch protection, release-gate workflow, the production GitHub Environment, the Railway CLI login and project, the gh pr merge permission rule and leftover worktrees. Read-only; proposes each fix and applies it only after the stakeholder agrees....Votes: 0GitHub stars: 2
- FixQuick lane for one small change: a bug against existing behavior, a text or style tweak, a small refactor or a dependency bump. Skips the BA, GATE 1/2 and story planning: the Team Lead turns the request into one XS/S task, then a developer, the reviewer, the Team Lead merge and a light QA check run as usual. Use when the stakeholder says fix, change, tweak, rename or bump something small; use the ba skill for new features or anything that needs product decisions.Votes: 0GitHub stars: 2
- PlanTeam Lead procedure: split approved stories (Backlog), needs-split tasks and QA bugs into small XS/S technical tasks with Files (expected), dependencies and Definition of Done, group them into parallel waves on the board and post the dispatch plan; recompute waves when developer slots are idle (rewave); put stories the stakeholder wants released into a milestone (milestone); turn one small stakeholder request into a single quick-lane task (quick); or, in merge mode, do the final check of a PR...Votes: 0GitHub stars: 2
- QaQA procedure: verify a merged task, bug or story in the QA column against every acceptance criterion and DoD item by running the full test suites, e2e and the real app on the latest main; pass it to Done with a test report, or file a bug sub-issue from the bug template and keep the task out of Done. Also re-verifies a task whose bugs are fixed and closes stories whose tasks are all Done. Use when items are waiting in QA.Votes: 0GitHub stars: 2
- ReportProgress report for the stakeholder: collect delivery metrics from the board and GitHub with metrics.sh (period or milestone), have the reporter draft a report with a 5-line plain-language summary and a metrics table where every number comes from the script, then publish it as a type:report issue and summarize it in the stakeholder's language. Use when the stakeholder asks how things are going, at the end of a run, or on a schedule.Votes: 0GitHub stars: 2
- ReviewCode review procedure for one PR in In Review: check size and scope, verify every acceptance criterion and DoD item has a test, review correctness and security against the review checklist, and post the verdict as a review comment (PASS adds review:passed for the Team Lead to merge; CHANGES sends the task back). Never approves or merges. Use when a PR is waiting for review.Votes: 0GitHub stars: 2
- RunPM orchestrator for squad: repeatedly read the board with next.sh and dispatch the right subagent for the highest-priority action (QA, Team Lead merge, review, rebase, planning, parallel developers by wave, deploy), relay gates and questions to the stakeholder, and stop at a requirements gate, when only GATE 3 is left, after max steps, or when nothing is left (then report). Use when the stakeholder says run, continue, or keep going, or on a schedule.Votes: 0GitHub stars: 2
- SetupInitialize squad in the current repository (or `quick`: board, labels and commands only, no deploys, in about two minutes): create or reuse the GitHub Projects board with the squad Status columns and Priority/Size/Wave/Agent/Attempts fields, create the labels, write .squad/config.yml, and configure merges, branch protection and .gitignore. Use the first time squad is used in a repository, when .squad/config.yml is missing, or when a board script reports missing ids.Votes: 0GitHub stars: 2