redteamlife
- 12 skills
- 0 followers
- 20 hours ago last updated
- ▌ Forge · redteamlife bundleGoverned workflow for AI-assisted coding on a real repo. Triggers: bounded tasks, file scope, task ledgers, claim-before-implement, evidence trails, critique/review/security gates, or multi-agent/multi-repo coordination. Use on any mention of "FORGE", `docs/forge/`, or governed development, or when agents drift outside scope. Not for one-off edits or unstructured review.
- ▌ Forge Plan · redteamlifeUse when the user asks to plan, break down, sequence, or add tasks in a repo containing `docs/forge/` or governed by FORGE. Shapes bounded tasks (scope, file_scope, dependencies, review needs) in the configured task source without implementing.
- ▌ Forge Ship · redteamlifeUse when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.
- ▌ Forge Memory · redteamlifeRead and maintain FORGE project memory across sessions. Use when retrieving recent patterns or failures before implementation, or when appending concise lessons, failure notes, and guardrail refinements after a task attempt.
- ▌ Forge Review · redteamlifeUse when the user asks to review work, a PR/MR, or whether a task is done in a repo containing `docs/forge/` or governed by FORGE. Runs the critique, security review, and evaluation gates in order; CI alone is not a review.
- ▌ Forge Critique · redteamlifeRun the FORGE critique pass for a completed or in-progress task. Use when checking for scope drift, undocumented assumptions, architecture conflicts, missing docs, or unaddressed failure modes before marking a task complete.
- ▌ Forge Bootstrap · redteamlife bundleBootstrap or migrate a repository into a FORGE skill-based workflow. Use when generating the initial `docs/forge/` files, reducing a document-heavy FORGE setup into a smaller skill-driven contract, or scaffolding the minimum governance files for a project.
- ▌ Forge Evaluation · redteamlifeApply FORGE definition-of-done and evidence checks to a task. Use when verifying completion gates, required testing, documentation updates, and whether the task is eligible to be marked complete and committed.
- ▌ Forge Execute Task · redteamlife bundleExecute one bounded FORGE task from repository-local governance docs. The primitive behind `forge-build`. Use when reading `docs/forge/` state, selecting the next incomplete task, enforcing task scope, implementing, running review gates, and stopping on ambiguity or failed gates.
- ▌ Forge Cross Project · redteamlifeBootstrap and maintain opt-in FORGE cross-project coordination docs for multi-repo projects with shared contracts, authority repos, peer repos, downstream repos, XPDs, and inbox proposals.
- ▌ Forge Tool Workflow · redteamlife bundleApply the FORGE private-dev and public-release workflow for tools. Use when scaffolding a tool repo, reasoning about preserve-history publishing, importing accepted public pull requests, or maintaining the dev-public repository split under FORGE governance.
- ▌ Forge Security Review · redteamlifeApply FORGE checklist-based security review to a task. Use when selecting a task-specific security checklist, reviewing trust-boundary and sensitive-data impact, and producing explicit pass, n-a, or escalated outcomes for each item.