railgun20001
UserHuman-in-the-loop project workflow skills for reliable AI-assisted software delivery.
Categories
Indexed Skills (8)
clarify-project-requirements
Clarify and baseline software project requirements before production design or implementation. Use for new projects, ambiguous feature requests, major scope changes, conflicting product sources, missing acceptance criteria, or when brand, engineering name, audience, platform, SEO, performance, security, privacy, accessibility, visual direction, prototype need, or scope boundaries are not yet accepted. Apply first-principles reasoning internally while speaking to users in plain language, and defer framework, database, API, hosting, and deployment questions when the initial product outcome is still vague.
deploy-project
Prepare, authorize, execute, verify, document, and roll back software deployment using the accepted technical and preliminary deployment solution. Use when accepted feature slices are ready for staging or production, when deployment configuration or runbooks must be completed, or when a user asks to build, publish artifacts, push images, migrate data, provision infrastructure, change DNS, or release. Require explicit authorization for each material external effect and distinguish local, CI, staging, production technical, and business acceptance evidence.
design-product-experience
Shape and validate a software product's information architecture, visual direction, interaction flows, interface states, responsiveness, accessibility, and optional minimal prototype before production implementation. Use after requirements are accepted, when interaction or visual behavior remains uncertain, when a user requests a prototype, or when existing designs and product behavior conflict.
design-technical-solution
Design and baseline a software project's production technology, architecture, data and API boundaries, security, SEO, performance, business and visual component strategy, testing, build, preliminary deployment, and required environment. Use after requirements and experience are accepted, when a major technical direction changes, when deployment assumptions are unclear, or before installing project tooling. Inspect the actual environment only after the solution is accepted, and install nothing without explicit consent.
develop-feature-slices
Plan, implement, test, review, and commit one observable feature slice at a time after requirements, experience, technical solution, and environment outcomes are accepted. Use when production development is authorized, when a large feature needs decomposition, when resuming an active slice, or when user corrections must be distilled into durable regression rules. Require human slice acceptance by default, provide self-check steps, preserve unrelated Git work, and create focused functional commits.
guard-artifact-scope
Prevent internal constraints from leaking into reader-facing artifacts or becoming unsupported product claims. Use if named. Invoke implicitly only when one artifact mixes product content with engineering, workflow, editorial, verification, or history constraints and a concrete unresolved scope conflict remains. Artifact type alone is not a trigger; skip routine phase-owned edits.
track-project-progress
Maintain the version-controlled THE-FIRST.md project index so decisions, document authority, human acceptance, feature slices, user feedback, verification evidence, commits, trackers, blockers, and next actions survive conversation changes. Use after meaningful project progress, phase or slice transitions, accepted feedback, commits, deployment events, or when a user asks for status, handoff, continuity, or progress reconciliation.
using-the-first
Start or resume a human-governed software project workflow before substantial implementation begins. Use when a user wants to initialize a project, turn an idea into software, add a substantial feature, recover work in a new conversation, or explicitly asks to use The First. Inspect project truth sources and THE-FIRST.md, restore current decisions and feedback, enforce phase gates, and route to the appropriate The First skill. For a vague initial idea, do not ask about frameworks, databases, APIs, hosting, or deployment in the first response.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.